Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | 2306 - recipe headers | Kartik K. Agaram | 2015-10-28 | 1 | -0/+1 |
| | | | | | | | | | | Once a student has gotten used to recipes and ingredients using the staged 'next-ingredient' approach there's no reason to avoid conventional function headers. As an added bonus we can now: a) check that all 'reply' instructions in a recipe are consistent b) deduce what to reply without needing to say so everytime c) start thinking about type parameters for recipes (generic functions!) | ||||
* | 2295 - drop first-class recipes and continuations | Kartik K. Agaram | 2015-10-28 | 1 | -1/+0 |
| | | | | Making life too complex at this time. | ||||
* | 2294 | Kartik K. Agaram | 2015-10-28 | 1 | -0/+1 |
| | | | | Bah, sick of CALL and continuations. | ||||
* | 2266 - drop experiment with generics | Kartik K. Agaram | 2015-10-07 | 1 | -1/+1 |
| | |||||
* | 2252 | Kartik K. Agaram | 2015-10-05 | 1 | -1/+1 |
| | | | | | | | | | | | | | | | | | | | | | | | | | I can't easily use generic containers without needing some syntax for generic recipes: push:number a:number, l:list:number which would be implemented as: T <- next-type a:T <- next-ingredient etc. Another concern: how to represent map<string, list<number>>? map::address:array:character::list:number where the '::' is just silently turned into ':'. Agh, all this is so baroque. All this while I've been trying to avoid getting into language design. All I want is some lightweight way to avoid security holes and memory corruption. But now it seems like I need facets to control compile-time activities and so on. | ||||
* | 2174 | Kartik K. Agaram | 2015-09-06 | 1 | -1/+2 |
| | |||||
* | 2153 | Kartik K. Agaram | 2015-09-05 | 1 | -1/+1 |
| | |||||
* | 2139 | Kartik K. Agaram | 2015-09-04 | 1 | -0/+1 |
| | |||||
* | 2080 | Kartik K. Agaram | 2015-08-26 | 1 | -0/+1 |
| | |||||
* | 2059 | Kartik K. Agaram | 2015-08-22 | 1 | -1/+1 |
| | |||||
* | 1960 | Kartik K. Agaram | 2015-08-09 | 1 | -2/+2 |
| | |||||
* | 1903 | Kartik K. Agaram | 2015-07-30 | 1 | -0/+5 |
| | |||||
* | 1868 - start using naked literals everywhere | Kartik K. Agaram | 2015-07-28 | 1 | -0/+2 |
| | | | | First step to reducing typing burden. Next step: inferring types. | ||||
* | 1780 - now we always reclaim local scopes | Kartik K. Agaram | 2015-07-13 | 1 | -1/+1 |
| | | | | | | But still no difference in either memory footprint or in running time. This will teach me -- for the umpteenth time -- to optimize before measuring. | ||||
* | 1774 | Kartik K. Agaram | 2015-07-13 | 1 | -1/+1 |
| | |||||
* | 1771 | Kartik K. Agaram | 2015-07-13 | 1 | -1/+2 |
| | |||||
* | 1646 | Kartik K. Agaram | 2015-06-25 | 1 | -1/+1 |
| | |||||
* | 1555 - mu.vim: distinguish control-flow from constants | Kartik K. Agaram | 2015-06-12 | 1 | -5/+7 |
| | | | | We also do this in regular C++ now. | ||||
* | 1506 | Kartik K. Agaram | 2015-05-28 | 1 | -1/+1 |
| | |||||
* | 1432 - contrast scenarios and recipes | Kartik K. Agaram | 2015-05-23 | 1 | -2/+3 |
| | |||||
* | 1410 | Kartik K. Agaram | 2015-05-20 | 1 | -1/+2 |
| | |||||
* | 1378 | Kartik K. Agaram | 2015-05-15 | 1 | -0/+1 |
| | |||||
* | 1333 | Kartik K. Agaram | 2015-05-10 | 1 | -3/+11 |
| | |||||
* | 1331 | Kartik K. Agaram | 2015-05-10 | 1 | -2/+4 |
| | |||||
* | 1327 - better error handling in chessboard | Kartik K. Agaram | 2015-05-10 | 1 | -1/+1 |
| | | | | | Also a bugfix in break to label, because I noticed the screen wasn't being cleaned up on quit. | ||||
* | vim highlighting for labels | Kartik K. Agaram | 2015-04-18 | 1 | -1/+2 |
| | |||||
* | 1093 - little more vim support for the old arc version | Kartik K. Agaram | 2015-04-17 | 1 | -0/+2 |
| | |||||
* | 1048 | Kartik K. Agaram | 2015-04-11 | 1 | -5/+5 |
| | |||||
* | 1025 - switch syntax highlighting to support c++ version | Kartik K. Agaram | 2015-04-06 | 1 | -6/+5 |
| | |||||
* | 561 - vim hack | Kartik K. Agaram | 2015-01-13 | 1 | -4/+7 |
| | |||||
* | 548 - hacky vim filetype for mu | Kartik K. Agaram | 2015-01-13 | 1 | -0/+37 |