Nondeterministic compilation and errors.

[kiljacken]

Currently a bug exists in ark-vm which changes behavior opon recompilation. I have no idea what is causing it or why, but it is clear that we should strive for deterministic compilation. The main offender is probably go maps, because randomizing map order is a great idea. So we have to revamp all uses of map iteration in the codegen.

[MovingtoMars]

I figured out the problem. The backing array for []s32 in the virtual machine is stack allocated. VirtualMachine holds a pointer to it, which we return from a function.

[MovingtoMars]

I think we may need to just remove non-fixed arrays altogether and use List instead.

[kiljacken]

No, that would remove all options of doing static bounds checking

On Mon, 29 Feb 2016 05:10 Liam, notifications@github.com wrote:

I think we may need to just remove non-fixed arrays altogether and use
List instead.

—
Reply to this email directly or view it on GitHub
#710 (comment).

[MovingtoMars]

The only other way I can see is disallowing non-fixed array literals. But, then how would strings work?

[kiljacken]

We just gotta make that "return address to something on the stack" semantic
pass

On Mon, Feb 29, 2016, 08:36 Liam notifications@github.com wrote:

The only other way I can see is disallowing non-fixed array literals. But,
then how would strings work?

—
Reply to this email directly or view it on GitHub
#710 (comment).