about summary refs log tree commit diff stats
path: root/064list.mu
Commit message (Collapse)AuthorAgeFilesLines
* 4262 - literal 'null'Kartik Agaram2018-06-171-14/+14
|
* 4260 - make address coercions explicitKartik Agaram2018-06-161-2/+2
| | | | | 'deaddress' is a terrible name. Hopefully I'll come up with something better.
* 4134 - 'input' = 'ingredient'Kartik K. Agaram2017-12-031-12/+12
|
* 4008Kartik K. Agaram2017-09-251-3/+2
| | | | | Allow list `push` operation to save result in a new list rather than mutate the existing list.
* 3893Kartik K. Agaram2017-05-291-34/+34
|
* 3881 - allow students to turn sandboxes into recipesKartik K. Agaram2017-05-271-1/+14
| | | | Thanks Juan Crispin Hernandez for the suggestion.
* 3828 - make buffers shape-shifting (generic)Kartik K. Agaram2017-04-181-3/+3
|
* 3808 - 'length' for duplex listsKartik K. Agaram2017-03-311-4/+7
|
* 3656Kartik K. Agaram2016-11-101-2/+2
| | | | | | | | | | | | | | Periodic cleanup to replace 'reply' with 'return' everywhere in the repo. I use 'reply' for students to help reinforce the metaphor of function calls as being like messages through a pipe. But that causes 'reply' to get into my muscle memory when writing Mu code for myself, and I worry that that makes Mu seem unnecessarily alien to anybody reading on Github. Perhaps I should just give it up? I'll try using 'return' with my next student.
* 3514Kartik K. Agaram2016-10-181-4/+5
| | | | | | | | Let's constrain 'push' on lists to always modify its ingredient. That makes some possibilities more verbose, such as lists that share a common tail. But may be worthwhile to get better errors in the common use-case.
* 3429 - standardize Mu scenariosKartik K. Agaram2016-09-281-31/+34
| | | | | | | | | | | | | A long-standing problem has been that I couldn't spread code across 'run' blocks because they were separate scopes, so I've ended up making them effectively comments. Running code inside a 'run' block is identical in every way to simply running the code directly. The 'run' block is merely a visual aid to separate setup from the component under test. In the process I've also standardized all Mu scenarios to always run in a local scope, and only use (raw) numeric addresses for values they want to check later.
* 3423Kartik K. Agaram2016-09-271-1/+9
|
* 3422Kartik K. Agaram2016-09-271-1/+1
| | | | | | | | | | Stop checking the number of ingredients and products when picking shape-shifting recipes. That's more consistent with how we handle regular recipes, and we still get errors in all the examples I can think of: reverse # no ingredients or products n:num <- length # no ingredients; products don't provide type
* 3418 - some functions contributed by Caleb CouchKartik K. Agaram2016-09-271-0/+28
|
* 3389Kartik K. Agaram2016-09-171-37/+37
|
* 3386Kartik K. Agaram2016-09-171-5/+5
|
* 3385Kartik K. Agaram2016-09-171-10/+10
|
* 3379Kartik K. Agaram2016-09-171-34/+34
| | | | Can't use type abbreviations inside 'memory-should-contain'.
* 3341Kartik K. Agaram2016-09-121-2/+2
| | | | | | | Process type abbreviations in function headers. Still a couple of places where doing this causes strange errors. We'll track those down next.
* 3058 - 'remove' for listsKartik K. Agaram2016-06-161-0/+112
|
* 3057 - 'insert' for listsKartik K. Agaram2016-06-161-0/+89
|
* 3055Kartik K. Agaram2016-06-131-0/+110
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-30 09:57:05 +0000
ass="w"> get the opportunity to # return. Calling functions should stop calling its continuation after this # point. return-continuation-until-mark 100/mark, -1, done? assert false, [called too many times, ran out of continuations to return] ]