New compiler

amp

Any expert JS’ers here? We’re merging the new TW compiler to AmpMod; see

Now we have an excuse to change AmpMod 0.3 to 1.0. Or even postpone the release of 0.3, but we want to make it a Christmas present, so…

unconstructable13

amp Now we have an excuse to change AmpMod 0.3 to 1.0

I still don’t want to change AmpMod 0.3 to 1.0, and we wouldn’t be able to, anyway, for the following reasons:
We still have to fix some of the array blocks (notably the array contains ()? boolean) and most of the extensions are completely broken (like the BeepBox player and the Legacy Lists). If none of these get fixed until the release of 0.3, I’m not changing my mind
Sorry if I sounded a bit rude

amp

unconstructable13 but this would be a complete rewrite of ampmod from the currennt TurboWarp code, so we can redo arrays and various extension APIs all from scratch

amp

i have decided to not rewrite ampmod, but i will potentially rewrite the VM in particular

unconstructable13

amp why the VM?

amp

unconstructable13 because that’s where the compiler lives
the entire point of this VM rewrite is to gain advantages from TW’s new compiler

amp

If upstream merging gets harder we might have to rewrite AmpMod.

amp

I fixed a poor compiler modding practice in this rewrite.
arrays.empty used to be compiled like any other non-constant block which adds overhead, especially considering how it reports only one value ([]).
I have fixed this and it is now a constant.

amp

@o97doge can I have help fixing this weird bug where Arrays blocks in the new compiler are strangely acting as if they are stack blocks? (the error says “Unknown stack block” — I have added all the code for the Arrays blocks in the input functions of the compiler)

amp

i’ve put a band-aid on the issue by moving the array blocks to the compat layer
also i added Cast.toList and surprisingly this made arrays much less buggy than in 0.2.2 (i used an API with that name but didn’t realise it wasn’t real, adding it fixed everything and makes life easier for ext devs)

amp

case blocks will be postponed to 0.4 due to complexity

amp

I think I’ve added all of the blocks to the new compiler (except for some blocks that have been postponed to 0.4). Just need to copy things like the amp api back here.

amp

If anyone was wondering, I postponed some of the blocks because their current implementations were broken.

Community

Resources

Policy