fix: perf, revert array, shift

[hugomrdias]

/cc @MaxGraey
do you have any idea why the Array version doesn't work?
also i can't find any docs in the @inline decorators were they removed ?

[MaxGraey]

Suggested change

	const cleanArr = []
	for (let i = 0; i < processed.length; i++) {
	if(processed[i] === 0) break
	cleanArr[i] = processed[i];
	}
	return cleanArr
	const end = processed.indexOf(0);
	return end >= 0 ? processed.subarray(0, end) : processed;

[MaxGraey]

Much better swap this. So alloc and release will be in LIFO order.

Suggested change

	__release(lengthsPtr)
	__release(pointer)
	__free(pointer)
	__free(lengthsPtr)

Because currently used stub runtime, not full or half

[hugomrdias]

I changed to full, why __free what's the difference?

[MaxGraey]

All this described in docs: https://docs.assemblyscript.org/details/runtime#runtime-variants

in short full / half use RC/GC runtime, stub/none just manual memory managment and retain / release just stubs in this case

[hugomrdias]

Read that already I just can't find the __free function, I would prefer to use stub and manage memory manually.

[hugomrdias]

With full you still need to tell wasm to __retain and after __release so it's kinda manual.
Any docs on how to go full manual with stub/none runtime?

[MaxGraey]

With full you still need to tell wasm to __retain and after __release

It's only for js / host side because we can't handle in this case memory automatically. But internally (in AS) you don't need call release / retain because compiler do this by himself (same as in Swift which used ARC)

[MaxGraey]

do you have any idea why the Array version doesn't work?

Array has slightly different layout and require __getArray instead __getUint32Array. But better use typed arrays when pass between host and wasm. It usually has faster interop.