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, 4 insertions, 4 deletions

diff --git a/083scenario_screen_test.mu b/083scenario_screen_test.mu
index 9679e9cf..a135984a 100644
--- a/083scenario_screen_test.mu
+++ b/083scenario_screen_test.mu
@@ -4,7 +4,7 @@ scenario print-character-at-top-left-2 [
   assume-screen 3/width, 2/height
   run [
     1:character <- copy 97/a
-    screen:address:screen <- print screen:address:screen, 1:character/a
+    screen:address:shared:screen <- print screen:address:shared:screen, 1:character/a
   ]
   screen-should-contain [
     .a  .
@@ -17,11 +17,11 @@ scenario clear-line-erases-printed-characters-2 [
   run [
     # print a character
     1:character <- copy 97/a
-    screen:address:screen <- print screen:address:screen, 1:character/a
+    screen:address:shared:screen <- print screen:address:shared:screen, 1:character/a
     # move cursor to start of line
-    screen:address:screen <- move-cursor screen:address:screen, 0/row, 0/column
+    screen:address:shared:screen <- move-cursor screen:address:shared:screen, 0/row, 0/column
     # clear line
-    screen:address:screen <- clear-line screen:address:screen
+    screen:address:shared:screen <- clear-line screen:address:shared:screen
   ]
   screen-should-contain [
     .     .