about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* 4144Kartik K. Agaram2017-12-071-23/+23
|
* 4143Kartik K. Agaram2017-12-071-22/+24
|
* 4142Kartik K. Agaram2017-12-051-8/+6
|
* 4141Kartik K. Agaram2017-12-051-20/+21
| | | | | Cleaner way to redo commit 2479 from just over two years ago, fixing scenario specialize_recursive_shape_shifting_recipe.
* 4140Kartik K. Agaram2017-12-051-1/+1
|
* 4139Kartik K. Agaram2017-12-055-28/+15
|
* 4138Kartik K. Agaram2017-12-054-5/+5
|
* 4137 - perform specialization on indirect callsKartik K. Agaram2017-12-042-9/+39
| | | | https://lobste.rs/s/esqphf/what_are_you_working_on_this_week#c_ajgfim
* 4136Kartik K. Agaram2017-12-042-4/+5
|
* 4135Kartik K. Agaram2017-12-032-2/+2
|
* 4134 - 'input' = 'ingredient'Kartik K. Agaram2017-12-03139-1449/+1517
|
* 4133Kartik K. Agaram2017-11-2510-146/+196
|
* 4132Kartik K. Agaram2017-11-191-4/+2
| | | | | | Simplify the implementation of calling continuations. Since we don't support next-ingredient on continuations, might as well not bother with all that call housekeeping for ingredients.
* 4131Kartik K. Agaram2017-11-192-9/+49
| | | | | | | | | Bugfix: I hadn't been allowing continuations to be copied. Deepens our initial sin of managing the Mu call stack implicitly in the C interpreter. Since the call stack was implicit, continuations had to be implicit as well. Since continuations aren't in Mu's memory, we have to replicate refcounting logic for them.
* 4130Kartik K. Agaram2017-11-191-34/+34
|
* 4129Kartik K. Agaram2017-11-191-2/+2
| | | | map::operator[](k) is indeed equivalent to (*((this->insert(make_pair(k,mapped_type()))).first)).second
* 4128Kartik K. Agaram2017-11-191-0/+1
|
* 4127Kartik K. Agaram2017-11-191-9/+9
|
* 4126Kartik K. Agaram2017-11-191-6/+1
|
* 4125Kartik K. Agaram2017-11-191-0/+15
|
* 4124Kartik K. Agaram2017-11-191-6/+3
|
* 4123Kartik K. Agaram2017-11-162-36/+18
|
* 4122Kartik K. Agaram2017-11-1513-1242/+1266
|
* 4121Kartik K. Agaram2017-11-151-0/+8
|
* 4120Kartik K. Agaram2017-11-101-0/+8
| | | | Support explicit conversions from number to character.
* 4119Kartik K. Agaram2017-11-104-4/+12
| | | | Running example programs after a long time.
* 4118Kartik K. Agaram2017-11-062-291/+293
|
* 4117 - done with delimited continuationsKartik K. Agaram2017-11-0616-842/+1019
| | | | | At least this particular implementation of them. Let's play with them now for a while, see if they're fully equivalent to shift/reduce.
* 4116 - support calling continuations with argumentsKartik K. Agaram2017-11-063-7/+45
| | | | | | Surprisingly small change, considering how long it took me and how mind-bending it was. 'return-continuation-until-mark' now behaves like both call and return instructions, which made it hard to reason about.
* 4115Kartik K. Agaram2017-11-061-3/+5
|
* 4114Kartik K. Agaram2017-11-051-59/+39
|
* 4113Kartik K. Agaram2017-11-052-288/+294
|
* 4112Kartik K. Agaram2017-11-052-26/+18
|
* 4111Kartik K. Agaram2017-11-051-0/+3
|
* 4110 - add continuations to docsKartik K. Agaram2017-11-056-5/+373
|
* 4109Kartik K. Agaram2017-11-0541-1091/+1222
|
* 4108Kartik K. Agaram2017-11-051-1/+2
|
* 4107Kartik K. Agaram2017-11-052-0/+75
| | | | Return other values along with the current continuation.
* 4106Kartik K. Agaram2017-11-0310-15/+14
|
* 4105Kartik K. Agaram2017-11-031-4/+4
|
* 4104Kartik K. Agaram2017-11-0323-73/+73
| | | | | Stop hardcoding Max_depth everywhere; we had a default value for a reason but then we forgot all about it.
* 4103 - continuations no longer cause memory corruptionKartik K. Agaram2017-11-034-5/+171
|
* 4102Kartik K. Agaram2017-11-0154-4738/+4816
|
* 4101Kartik K. Agaram2017-11-011-2/+2
|
* 4100Kartik K. Agaram2017-11-011-1/+1
|
* 4099Kartik K. Agaram2017-11-018-71/+128
| | | | | | | | | | | | | | Generalize commit 4089 to arbitrary closures, and not just the current 'space' or call frame. Now we should be treating spaces just like any other data structure, and reclaiming all addresses inside them when we need to. The cost: all spaces must now specify what recipe generated them (so they know how to interpret the array of locations) using the /names property. We can probably make this ergonomic with a little 'type inference'. But at least things are safe now.
* 4098Kartik K. Agaram2017-10-303-8/+63
| | | | | | | | | Finally, make the seemingly-trivial change to buffer methods that I was envisioning 2 days ago. I still have zero confidence in our heuristic for picking the generic method to specialize for a call-site. Waiting for issues to reveal themselves.
* 4097Kartik K. Agaram2017-10-301-21/+34
| | | | | | | Don't silently ignore ties we failed to break when matching generic functions to calls. Now we can start working on the bug that triggered commits 4092-4097.
* 4096Kartik K. Agaram2017-10-301-6/+6
|
* 4095Kartik K. Agaram2017-10-301-1/+1
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-07-04 10:36:37 +0000