Should machine be exposed as a package?

[michealroberts]

Just a question, what are the complexities of exposing "machine" as a package, e.g., we import from https://tinygo.org/x/machine rather than how it is currently imported?

I just wonder if we should only purely use tinygo as a compiler, and not ... shall we say, "amend" the stdlib, e.g., such that we can run without any modifications, e.g.,:

//go:build tinygo // +build tinygo

etc

Just an idea. Hoping someone can school my as to why this isn't possible.