Skip to content

Incorrect upvalue behavior #3

@gabearro

Description

@gabearro

Upvalues are behaving incorrectly. At the moment, there is either too much isolation where an upvalue that should be a reference is being treated as a copied value or vice versa. Not sure which one is the issue but it seems to have broken when I rewrote the part of the VM that handles activation records

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingregressionsomething that worked before regressed

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions