AssemblyScript

It is awkward, but TypeScript officially supports using .js in import specifiers, like so:

import {foo} from './path/to/some/file.js'
console.log(foo)

where ./path/to/some/file.js does not actually exist, but th

If a new Environment is created, processes inside of it will not have access to any command line arguments or environment variables by default. They need to be added to the ConfigEnv struct from which the Environment is created. Currently this is only possible from the host, but is not exposed as a [host function

This would vastly help the Dev experience for game developers 😄 They cansimply host a local server that hosts their game, and the debugger can just try to grab it and auto run 😄

Need to add a blurb about the test entry points and all spec files being imported.

The font bitmap has empty space reserved for ASCII characters 0x80 through 0xA0.

We should use that space for something, like icons for WASM-4 controller buttons, or generic sprites like stars/hearts/etc.

Games can then use hex string literals to easily display these:

text("Press \x80 to jump!", 0, 0);

https://github.com/ColinEberhardt/assemblyscript-regex/blob/main/.prettierignore

it would be good to find a fix / workaround for this.

• Benchmark suite.
• Compare with Rust.
• Compare with incoming javascript's BigInt.

• We need to explore some ways to extract the ask! code from the as compiler internal. At present, it can be completely written as an independent ts project, in my personal opinion.
• We should define the metadata.json's spec class rather than generate it by template engine. It's hard to maintain and test it.
• The code in some places is hard-coded, and parameterization and configurati