From 455fbac64f101b05f7eaca89b84470569e4df3fd Mon Sep 17 00:00:00 2001 From: "Kartik K. Agaram" Date: Tue, 19 Jan 2016 23:18:03 -0800 Subject: 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. --- 072array.mu | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to '072array.mu') diff --git a/072array.mu b/072array.mu index 03348c3a..147ec0bf 100644 --- a/072array.mu +++ b/072array.mu @@ -1,7 +1,7 @@ scenario array-from-args [ run [ - 1:address:array:character <- new-array 0, 1, 2 - 2:array:character <- copy *1:address:array:character + 1:address:shared:array:character <- new-array 0, 1, 2 + 2:array:character <- copy *1:address:shared:array:character ] memory-should-contain [ 2 <- 3 # array length @@ -12,7 +12,7 @@ scenario array-from-args [ ] # create an array out of a list of scalar args -recipe new-array [ +recipe new-array -> result:address:shared:array:character [ local-scope capacity:number <- copy 0 { @@ -22,7 +22,7 @@ recipe new-array [ capacity <- add capacity, 1 loop } - result:address:array:character <- new character:type, capacity + result <- new character:type, capacity rewind-ingredients i:number <- copy 0 { -- cgit 1.4.1-2-gfad0