2576 - distinguish allocated addresses from others

This is the one major refinement on the C programming model I'm planning
to introduce in mu. Instead of Rust's menagerie of pointer types and
static checking, I want to introduce just one new type, and use it to
perform ref-counting at runtime.

So far all we're doing is updating new's interface. The actual
ref-counting implementation is next.

One implication: I might sometimes need duplicate implementations for a
recipe with allocated vs vanilla addresses of the same type. So far it
seems I can get away with just always passing in allocated addresses;
the situations when you want to pass an unallocated address to a recipe
should be few and far between.

1 files changed, 1 insertions, 1 deletions

diff --git a/055parse_tree.cc b/055parse_tree.cc
index 947093b9..f9b15adb 100644
--- a/055parse_tree.cc
+++ b/055parse_tree.cc
@@ -71,7 +71,7 @@ container bar [
 
 :(scenario dilated_reagent_with_new)
 recipe main [
-  x:address:address:number <- new {(address number): type}
+  x:address:shared:address:number <- new {(address number): type}
 ]
 +new: size of <"address" : <"number" : <>>> is 1