Assemblyscript: Publish assemblyscript and @assemblyscript/loader to npm

[xtuc]

The loader here https://github.com/AssemblyScript/assemblyscript/blob/dc0f271fc239a3d27d67ffdefe4a61343a5bb2ba/lib/loader/package.json#L2

is not available on npm: https://www.npmjs.com/package/@assemblyscript/loader.

[xtuc]

And what's the difference with https://www.npmjs.com/package/assemblyscript-loader?

[dcodeIO]

Both the assemblyscript and the assemblyscript-loader package on npm are outdated and belong to the old prototype. Master isn't on npm yet, neither the compiler nor the new loader.

[xtuc]

Ok. Also it seems that array utils (ptr = createArray for example) have not been implemented from the prototype.

Should we leave this open?

[dcodeIO]

Sure, changed the title to keep track of it. Once it's known that GC isn't completely broken, I think we can go ahead and publish a first version of the new compiler and utilities.

[MaxGraey]

And follow semver convention?

[dcodeIO]

Afaik, all 0.X versions are treated like an "unstable" major version. So going with 0.5.0 should be fine, unless I'm mistaken.

[xtuc]

Yes, that's my understanding of semver too. Thanks for the work!

[xtuc]

Shouldn't the GC be behind a flag btw?

[MaxGraey]

Currently GC (ugc) require manual importing anyway. As I understand when allocator and gc will be provide explicitly by default this flag will be appear

[JounQin]

If the npm versions are outdated, then why are you not publishing the latest versions to npm?

[cdetrio]

Sure, changed the title to keep track of it. Once it's known that GC isn't completely broken, I think we can go ahead and publish a first version of the new compiler and utilities.

It's one year later, is the GC still completely broken?

[MaxGraey]

@cdetrio GC was completely rewritten and use ARC for acyclic references and GC for cyclic references and should work more or less stable for now

[MaxGraey]

Closed in favour #750