| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | 2576 - distinguish allocated addresses from others | Kartik K. Agaram | 2016-01-19 | 1 | -68/+66 |
| | | | | | | | | | | | | | | | | | 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. | ||||
| * | 2562 | Kartik K. Agaram | 2016-01-17 | 1 | -1/+1 |
| | | | | | | | | | | | | | We want to use the type 'recipe' for recipe *variables*, because it seems nicer to say `recipe number -> number` rather than recipe-ordinal, etc. To support this we'll allow recipe names to be mentioned without any type. This might make a couple of places in this commit more brittle. I'm dropping error messages, causing them to not happen in some situations. Maybe I should just bite the bullet and require an explicit :recipe-literal. We'll see. | ||||
| * | 2476 | Kartik K. Agaram | 2015-11-27 | 1 | -1/+1 |
| | | |||||
| * | 2460 - headers for remaining recipes | Kartik K. Agaram | 2015-11-18 | 1 | -35/+21 |
| | | |||||
| * | 2430 - make room for more transforms | Kartik K. Agaram | 2015-11-13 | 1 | -0/+373 |