about summary refs log tree commit diff stats
path: root/084console.mu
Commit message (Collapse)AuthorAgeFilesLines
* 2864 - replace all address:shared with just addressKartik K. Agaram2016-04-241-10/+10
| | | | | | | 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-3/+3
|
* 2844 - purge get-address from all layersKartik K. Agaram2016-04-161-8/+6
| | | | | Only apps left now, and the wait-for-location uses in the channel primitives.
* 2798 - experiment: split channels into two endsKartik K. Agaram2016-03-191-1/+1
| | | | | | | | | | This way when you pass one end to a function or routine, you can implicitly give it the right to either read or write the channel, but not both. The cost: code gets more convoluted, names get more convoluted. You can see this in particular in the test for buffer-lines. Let's see how it goes..
* 2784 - make channels genericKartik K. Agaram2016-03-141-1/+1
| | | | | | I've ignored Mu's concurrency primitives for a while, but they're starting to return to front-and-center as I work on the file system interfaces.
* 2735 - define recipes using 'def'Kartik K. Agaram2016-03-081-14/+14
| | | | | | | | | | | | 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-11/+11
| | | | | | | | | | | | | | | | 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.
* 2612Kartik K. Agaram2015-11-291-9/+9
|
* 2468 - overload print-character as just 'print'Kartik K. Agaram2015-11-211-1/+1
|
* 2460 - headers for remaining recipesKartik K. Agaram2015-11-181-26/+21
|
* 2430 - make room for more transformsKartik K. Agaram2015-11-131-0/+113