dcodeIO

Related: https://github.com/ColinEberhardt/assemblyscript-regex/commit/c6118315ef0f9081b84fa511c49f5cb189143ea6 cc @ColinEberhardt

A "converting from TS to AS" kind of guide can become quite complex when getting into the details. It *can* be easy if the existing code base permits (code cleverly...

Do you have thoughts on where and how to document the behavior ideally?

The property is [private](https://github.com/AssemblyScript/assemblyscript/blob/d884ac8032b2bfa0caf26d4dc11d99c5a9543c13/std/assembly/array.ts#L50) on normal Arrays, though this restriction is currently not enforced. Accessing it nonetheless is technically possible but considered unsafe. Within the standard library, we'd do something...

Depending on how complex the program is, and which optimizations options are used, would this hang the main thread whenever something is clicked?

Hmm, good question. Haven't had a need for this yet, but if it is useful to you then I'm happy to accept a PR :)

Should be possible. Maybe specifying `node-version: ""` already does the trick, or alternatively the default can be made an empty string with [the install script](https://github.com/dcodeIO/setup-node-nvm/blob/master/install.sh#L8-L9) skipping the explicit version setup.

Hmm, I thought https://github.com/dcodeIO/setup-node-nvm/commit/3fca218c735ab2d366213f72356e126e0a2fa57c would make it work. It essentially uses an empty node version by default, which should make nvm look up from `.nvmrc`. There's also a [simple test](https://github.com/dcodeIO/setup-node-nvm/blob/master/.github/workflows/nvmrc.yml)...

I guess this should be possible with a `cwd` option as proposed [here](https://github.com/dcodeIO/setup-node-nvm/pulls). Alternatively, making the `nvm` command callable manually should also work, so one can `cd` there and call...

A while ago I changed the install directory from $HOME/.nvm to $HOME/mynvm ([see](https://github.com/dcodeIO/setup-node-nvm/blob/3bc09a3f6f58358a453eccc31a88b0c661cba9f9/install.sh#L3)). Looks a bit silly, but should work around the problem by replacing any potentially existing nvm install...