| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | 2778 - fix all layers | Kartik K. Agaram | 2016-03-14 | 1 | -63/+0 |
| | | |||||
| * | 2777 - pass literal strings into functions | Kartik K. Agaram | 2016-03-13 | 1 | -4/+4 |
| | | |||||
| * | 2776 | Kartik K. Agaram | 2016-03-13 | 1 | -8/+7 |
| | | |||||
| * | 2775 - test rewrite-stash transform | Kartik K. Agaram | 2016-03-13 | 1 | -0/+12 |
| | | |||||
| * | 2773 - switch to 'int' | Kartik K. Agaram | 2016-03-13 | 1 | -6/+6 |
| | | | | | This should eradicate the issue of 2771. | ||||
| * | 2656 | Kartik K. Agaram | 2016-02-14 | 1 | -0/+1 |
| | | |||||
| * | 2630 | Kartik K. Agaram | 2016-02-06 | 1 | -1/+1 |
| | | |||||
| * | 2576 - distinguish allocated addresses from others | Kartik K. Agaram | 2016-01-19 | 1 | -1/+1 |
| | | | | | | | | | | | | | | | | | 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. | ||||
| * | 2606 - handle cycles inside stash | Kartik K. Agaram | 2015-11-29 | 1 | -1/+1 |
| | | | | | | | | | | The idea is that to-text-line should truncate blindly past some threshold, even if to-text isn't smart enough to avoid infinite loops. Maybe I should define a 'truncating buffer' which stops once it fills up. That would be an easy way to eliminate all infinite loops in to-text-line. | ||||
| * | 2504 - support to-text in 'stash' | Kartik K. Agaram | 2015-11-28 | 1 | -0/+51 |