about summary refs log tree commit diff stats
path: root/043space.cc
diff options
context:
space:
mode:
authorKartik K. Agaram <vc@akkartik.com>2016-03-04 10:19:54 -0800
committerKartik K. Agaram <vc@akkartik.com>2016-03-04 10:26:00 -0800
commit078f48f5e0749c94ad17465111b1f76eae41190a (patch)
tree3a6c2800faf6e5f23cff3a677737b051c66edd02 /043space.cc
parentf343a9212d93f70018e84c0eb5a537e30a49b3f0 (diff)
downloadmu-078f48f5e0749c94ad17465111b1f76eae41190a.tar.gz
2727 - don't ignore /space: in immutability checks
Right now there's now way to tag variables from surrounding spaces
(lexical scopes) as immutable. Should I assume they're immutable unless
the surrounding space is passed out in addition to passed in? What if it
comes from a global?

Or should we explicitly specify modified variables in the header, even
if they'll never be saved anywhere?

We don't use these features much yet, wait until we need it. Mutability
checks are an optional layer and can't cause memory corruption. Lack of
type-checking in the global space, however, *can* cause memory
corruption. That's the biggest open issue right now.
Diffstat (limited to '043space.cc')
0 files changed, 0 insertions, 0 deletions