about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
...
* 3662Kartik K. Agaram2016-11-101-2/+2
|
* 3661Kartik K. Agaram2016-11-101-22/+24
| | | | Another place I missed in commit 3309.
* 3660Kartik K. Agaram2016-11-101-8/+11
| | | | | Fix a place I forgot to update in commit 3309, moving to the new type_tree representation.
* 3659Kartik K. Agaram2016-11-101-1/+1
|
* 3658Kartik K. Agaram2016-11-101-23/+23
|
* 3657 - better error messageKartik K. Agaram2016-11-102-3/+15
| | | | Thanks Ella Couch for reporting this.
* 3656Kartik K. Agaram2016-11-1020-79/+92
| | | | | | | | | | | | | | 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.
* 3655Kartik K. Agaram2016-11-081-1/+1
|
* 3654Kartik K. Agaram2016-11-088-41/+68
| | | | | | | | Follow-up to commit 3321: move get_base_type() more thoroughly to layer 55. The notion of a base_type doesn't really make sense before we introduce type ingredients and shape-shifting containers, and it simplifies early layers a *lot* even including the cost of that *ugly* preamble in layer 55 to retrofit all the places.
* 3653Kartik K. Agaram2016-11-085-5/+27
| | | | | | | | | Don't crash on bad types. I need to be more careful in distinguishing between the two causes of constraint violations: bad input and internal bugs. Maybe I should create a second assert() to indicate "this shouldn't really be an assert, but I'm too lazy to think about it right now."
* 3652Kartik K. Agaram2016-11-084-14/+23
| | | | | size_of(type_tree*) is a mess; clean it up with an eye to the final tangled version.
* 3651Kartik K. Agaram2016-11-082-2/+29
| | | | | | I was under the impression that I only needed static array lengths for container members, but these are *payload* types for allocations. So we need to compute the size of a dynamic array.
* 3650 - first of a couple of holes in refcountingKartik K. Agaram2016-11-081-0/+58
| | | | We weren't checking within (static) array elements for addresses.
* 3649Kartik K. Agaram2016-11-081-6/+0
|
* 3648Kartik K. Agaram2016-11-081-1/+1
|
* 3647Kartik K. Agaram2016-11-081-2/+3
|
* 3646Kartik K. Agaram2016-11-071-22/+22
|
* 3645Kartik K. Agaram2016-11-074-40/+26
| | | | | | Extract a helper to compute the element type of an array. As a side effect, the hack for disambiguating array:address:number and array:number:3 is now in just one place.
* 3644Kartik K. Agaram2016-11-072-71/+80
| | | | Eject some array-related code out of the container layer.
* 3643Kartik K. Agaram2016-11-0714-31/+31
| | | | | Standardize on calling literate waypoints "Special-cases" rather than "Cases". Invariably there's a default path already present.
* 3642Kartik K. Agaram2016-11-0610-119/+167
| generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-10-21 16:57:09 +0000