Remove cell#3
Merged
Merged
Conversation
another nail in Cell's coffin. this adds a layer of indirection so assignment doesn't depend on a mutable value inside a Cell
not yet finished, still some crashes and the semantics of assigning to $ are still wrong.
store both the Value and the LValue. reading returns the Value directly, writing goes via the LValue
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
semantic changes this makes:
$inENDFILEis set to whatever it was at the end ofBEGINFILE.arrays are now always copied by reference in function calls. that wasn't intentional, previously
Valuestored arrays as[]*Cell. mutating items in the array would work:prints
[4]But growing the array would not:
prints
[]trying to read
$inBEGINorENDis now a runtime error (unknown variable $).