about summary refs log tree commit diff stats
path: root/072recipe.cc
Commit message (Collapse)AuthorAgeFilesLines
* 4262 - literal 'null'Kartik Agaram2018-06-171-1/+1
|
* 4260 - make address coercions explicitKartik Agaram2018-06-161-1/+1
| | | | | 'deaddress' is a terrible name. Hopefully I'll come up with something better.
* 4224 - fill an old hole in static dispatchKartik K. Agaram2018-03-141-3/+162
| | | | Resolve ambiguous calls when copying (overloaded) recipe literals to variables.
* 4223Kartik K. Agaram2018-03-141-4/+1
|
* 4214Kartik K. Agaram2018-02-211-1/+2
|
* 4179 - experiment: rip out memory reclamationKartik K. Agaram2018-01-031-3/+0
| | | | | | | | | | | | | | | | | | | | | I have a plan for a way to avoid use-after-free errors without all the overheads of maintaining refcounts. Has the nice side-effect of requiring manual memory management. The Mu way is to leak memory by default and build tools to help decide when and where to expend effort plugging memory leaks. Arguably programs should be distributed with summaries of their resource use characteristics. Eliminating refcount maintenance reduces time to run tests by 30% for `mu edit`: this commit parent mu test: 3.9s 4.5s mu test edit: 2:38 3:48 Open questions: - making reclamation easier; some sort of support for destructors - reclaiming local scopes (which are allocated on the heap) - should we support automatically reclaiming allocations inside them?
* 4160 - named marks for delimited continuationsKartik K. Agaram2017-12-151-5/+3
| | | | | Hypothesis: this is needed to build McCarthy's amb operator. https://rosettacode.org/wiki/Amb
* 4151 - specializing calls returning continuationsKartik K. Agaram2017-12-071-2/+11
|
* 4145 - specializing recipe literals in `call`Kartik K. Agaram2017-12-071-24/+58
|
* 4144Kartik K. Agaram2017-12-071-23/+23
|
* 4137 - perform specialization on indirect callsKartik K. Agaram2017-12-041-0/+25
| | | | https://lobste.rs/s/esqphf/what_are_you_working_on_this_week#c_ajgfim
* 4106Kartik K. Agaram2017-11-031-1/+1
|
* 3991 - start work on making continuations safeKartik K. Agaram2017-09-101-0/+396
Plan: 1. Fix a hole where addresses are shared between routines when passed in as arguments to `start-running`. 2. Switch to a new approach to refcount management: instead of updating refcounts when writing products of instructions by default, increment refcounts inside instructions by default and decrement refcounts in caller. More details in future when I actually implement this. 3. Now we shouldn't need a distinction between `new-default-space` and `local-scope`, and all functions can simply decrement refcounts of their default-space, consistently handling any refcounts in the space. At this point if all goes well, continuations should be safe! This commit is just preparation for step 1.