about summary refs log tree commit diff stats
path: root/edit/011-editor-undo.mu
Commit message (Collapse)AuthorAgeFilesLines
* 2580 - check product type of 'maybe-convert'Kartik K. Agaram2016-01-201-10/+10
| | | | I had to undo some over-zealous changes in 2576.
* 2576 - distinguish allocated addresses from othersKartik K. Agaram2016-01-191-379/+379
| | | | | | | | | | | | | | | | 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.
* 2471Kartik K. Agaram2015-11-221-4/+0
|
* 2446 - drop '-duplex' namespacing in recipesKartik K. Agaram2015-11-151-19/+19
| | | | Great that it just worked after the previous commit.
* 2388 - final layer of edit/ loaded successfullyKartik K. Agaram2015-11-071-37/+36
|
* 2374 - now edit works until layer 8Kartik K. Agaram2015-11-051-59/+59
|
* 2309Kartik K. Agaram2015-10-281-123/+123
|
* 2247 - type-check products of non-primitive recipesKartik K. Agaram2015-10-051-9/+9
| | | | | | | | We still can't check ingredient types, and even this is still a run-time check. We'll need to start tracking recipe signatures at some point. I've had to introduce a hack called /skiptypecheck. Time to get generics working.
* 2234 - check type of get's productKartik K. Agaram2015-10-021-9/+9
| | | | Already I'm finding type errors in the programming environment.
* 2179 - undo bugfixKartik K. Agaram2015-09-101-0/+21
|
* 2160Kartik K. Agaram2015-09-051-0/+2056