| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | 2085 - undo/redo now working for simple typing | Kartik K. Agaram | 2015-08-27 | 1 | -2/+5 |
| | | | | | | Not yet useable, because we never ever stop coalescing operations. That will happen when we introduce a second type of operation. | ||||
| * | 2084 | Kartik K. Agaram | 2015-08-27 | 1 | -1/+58 |
| | | |||||
| * | 2082 | Kartik K. Agaram | 2015-08-26 | 1 | -0/+16 |
| | | |||||
| * | 1909 - clean up all null pointers of that ilk | Kartik K. Agaram | 2015-07-31 | 1 | -36/+36 |
| | | |||||
| * | 1883 - type-deducing in more .mu files | Kartik K. Agaram | 2015-07-29 | 1 | -47/+47 |
| | | |||||
| * | 1869 - rename the /deref property to /lookup | Kartik K. Agaram | 2015-07-28 | 1 | -32/+32 |
| | | | | | Should be a little bit more mnemonic. | ||||
| * | 1868 - start using naked literals everywhere | Kartik K. Agaram | 2015-07-28 | 1 | -42/+42 |
| | | | | | First step to reducing typing burden. Next step: inferring types. | ||||
| * | 1780 - now we always reclaim local scopes | Kartik K. Agaram | 2015-07-13 | 1 | -6/+6 |
| | | | | | | | But still no difference in either memory footprint or in running time. This will teach me -- for the umpteenth time -- to optimize before measuring. | ||||
| * | 1773 - update all mu recipes to new-default-space | Kartik K. Agaram | 2015-07-13 | 1 | -6/+6 |
| | | | | | | Turns out to not affect memory utilization or run-time. At all. But still looks nicer and requires less fudging on our part. | ||||
| * | 1603 | Kartik K. Agaram | 2015-06-19 | 1 | -6/+15 |
| | | |||||
| * | 1602 | Kartik K. Agaram | 2015-06-19 | 1 | -21/+31 |
| | | | | | | I forgot to check for nulls before writing prev pointers in doubly linked lists. Tests were accidentally passing. | ||||
| * | 1594 - removing from start/end of duplex list | Kartik K. Agaram | 2015-06-18 | 1 | -4/+67 |
| | | | | | | | | | | | This uncovers an issue with this interface to duplex lists: the caller needs to check the result and invalidate any other pointers if it's null (i.e. the list is now empty) We *could* try to encapsulate the list in a header to help the caller manage header pointers. But heck, let's see if writing tests helps call-sites stay on the straight and narrow. | ||||
| * | 1593 | Kartik K. Agaram | 2015-06-18 | 1 | -0/+75 |
| | | |||||
| * | 1592 | Kartik K. Agaram | 2015-06-18 | 1 | -0/+36 |
| | | |||||
| * | 1591 | Kartik K. Agaram | 2015-06-18 | 1 | -3/+43 |
| | | |||||
| * | 1590 - inserting into doubly linked list | Kartik K. Agaram | 2015-06-18 | 1 | -0/+62 |
| | | |||||
| * | 1589 - doubly linked list | Kartik K. Agaram | 2015-06-18 | 1 | -0/+74 |