about summary refs log tree commit diff stats
path: root/edit/002-typing.mu
Commit message (Collapse)AuthorAgeFilesLines
* 3038 - track down a long-standing bugKartik K. Agaram2016-06-081-25/+56
| | | | | | | | | | | | | | | | | | | | | | | | | | | In some rare situations the editor would join a line with the next when it should simply wrap to the next screen row. Thanks Caleb and Ella Couch for finally running into a situation that was easy to reproduce. The scenario diffs are misleading on this commit. I had to: a) delete the obsolete 'editor-wraps-cursor-after-inserting-characters' because it was written back when a line just large enough to fit in a single line would not wrap: | | <-- screen boundary abcde These days it will wrap after making room for the wrap indicator: | | <-- screen boundary abcd↩ e b) rename editor-wraps-cursor-after-inserting-characters-2 to editor-wraps-cursor-after-inserting-characters-in-middle-of-line c) create a new scenario demonstrating the bug: editor-wraps-cursor-after-inserting-characters-at-end-of-line
* 2975Kartik K. Agaram2016-05-191-1/+1
| | | | Clean up this helper before we start redoing sandbox menubars.
* 2864 - replace all address:shared with just addressKartik K. Agaram2016-04-241-136/+136
| | | | | | | Now that we no longer have non-shared addresses, we can just always track refcounts for all addresses. Phew!
* 2861 - 'maybe-convert' no longer returns addressKartik K. Agaram2016-04-231-13/+13
|
* 2853 - purge get-address from edit/ appKartik K. Agaram2016-04-221-55/+66
| | | | Phew!
* 2735 - define recipes using 'def'Kartik K. Agaram2016-03-081-31/+31
| | | | | | | | | | | | I'm dropping all mention of 'recipe' terminology from the Readme. That way I hope to avoid further bike-shedding discussions while I very slowly decide on the right terminology with my students. I could be smarter in my error messages and use 'recipe' when code uses it and 'function' otherwise. But what about other words like ingredient? It would all add complexity that I'm not yet sure is worthwhile. But I do want separate experiences for veteran programmers reading about Mu on github and for people learning programming using Mu.
* 2576 - distinguish allocated addresses from othersKartik K. Agaram2016-01-191-136/+136
| | | | | | | | | | | | | | | | 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.
* layers 1 and 2 of edit/ now workingKartik K. Agaram2015-12-151-4/+4
|
* 2468 - overload print-character as just 'print'Kartik K. Agaram2015-11-211-3/+3
|
* 2446 - drop '-duplex' namespacing in recipesKartik K. Agaram2015-11-151-14/+14
| | | | Great that it just worked after the previous commit.
* 2417 - support mutable ingredients in headersKartik K. Agaram2015-11-101-1/+1
| | | | | | If a name repeats between ingredients, we raise an error. If a name repeats across ingredients and products, every call should share the same name across the corresponding ingredients and products.
* 2370 - layers 1-4 of edit are backKartik K. Agaram2015-11-051-69/+58
| | | | | | | | | | | | One nice consequence of all my deduction of reply ingredients is that I can insert the same fragment into recipes with different headers, and everything works as long as reply instructions are implicitly deduced. One thing I had to fix to make this work was to move reply-deduction out of rewrite rules and turn it into a first-class transform, so that it happens after tangling. I'm glad to see the back of that hack inside <scroll-down>.
* 2309Kartik K. Agaram2015-10-281-63/+63
|
* 2173 - 'main' for 'mu edit' running layers 1 and 2Kartik K. Agaram2015-09-061-1/+42
| | | | | | Layer 2 provides an almost fully functioning interactive editor: $ ./mu edit/00[12]* -- abcdef
* 2156 - split edit.mu into multiple filesKartik K. Agaram2015-09-051-0/+1012
Now you can bring up the programming environment by saying: $ mu edit The files under edit aren't yet *layers*, though, they have a few dependencies that we need to clean up.