about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* 2336Kartik K. Agaram2015-10-312-10/+21
| | | | Minor tweak: track all recipe variants.
* 2335Kartik K. Agaram2015-10-311-1/+1
|
* 2334Kartik K. Agaram2015-10-314-4/+31
|
* 2333Kartik K. Agaram2015-10-311-0/+8
|
* 2332Kartik K. Agaram2015-10-311-1/+21
|
* 2331 - generic recipe: first passing testKartik K. Agaram2015-10-312-0/+145
|
* 2330 - support generic containers in 'get'Kartik K. Agaram2015-10-301-4/+53
|
* 2329 - hacky start to generic containersKartik K. Agaram2015-10-302-0/+101
|
* 2328Kartik K. Agaram2015-10-301-3/+19
| | | | Forgot to run valgrind again. That triggered some trace cleanup as well.
* 2327Kartik K. Agaram2015-10-301-4/+1
|
* 2326Kartik K. Agaram2015-10-301-8/+8
|
* 2325Kartik K. Agaram2015-10-301-2/+1
|
* 2324 - static dispatch works with arcane headers!Kartik K. Agaram2015-10-291-8/+7
|
* 2323 - static dispatch!Kartik K. Agaram2015-10-293-1/+186
|
* 2322 - deduce types from recipe headerKartik K. Agaram2015-10-291-3/+47
|
* 2321 - more preparations for static dispatchKartik K. Agaram2015-10-2912-65/+75
| | | | | Deduce operation id from name during transform rather than load, so that earlier transforms have a chance to modify the name.
* 2320Kartik K. Agaram2015-10-291-51/+51
|
* 2319Kartik K. Agaram2015-10-291-2/+3
|
* 2318Kartik K. Agaram2015-10-291-1/+1
| | | | Forgot to run against valgrind.
* 2317Kartik K. Agaram2015-10-292-0/+0
|
* 2316 - preparing for static dispatchKartik K. Agaram2015-10-294-16/+28
|
* 2315Kartik K. Agaram2015-10-291-2/+2
|
* 2314 - final tweaks to traceKartik K. Agaram2015-10-293-2/+4
| | | | | | | | I checked these commands: $ mu x.mu $ grep "===" .traces/interactive $ grep "===\|---" .traces/interactive
* 2313Kartik K. Agaram2015-10-2912-35/+32
|
* 2312Kartik K. Agaram2015-10-294-5/+6
|
* 2311Kartik K. Agaram2015-10-2911-80/+85
|
* 2310 - add some more tracingKartik K. Agaram2015-10-293-4/+14
| | | | | | | | | | | I've been growing lax on white-box testing when it's one of the three big thrusts of this whole effort. Perhaps it was because I got too obsessed with keeping traces stable and didn't notice that stable doesn't mean "not changing". Or perhaps it's because I still don't have a zoomable trace browser that can parse traces from disk. Or perhaps $trace-browser is too clunky and discourages me from using it. Regardless, I need to make the trace useable again before I work much more on the next few rewriting transforms.
* 2309Kartik K. Agaram2015-10-2821-892/+892
|
* 2308 - auto-reply on fall-throughKartik K. Agaram2015-10-281-0/+30
|
* 2307Kartik K. Agaram2015-10-281-0/+5
|
* 2306 - recipe headersKartik K. Agaram2015-10-2810-16/+132
| | | | | | | | | | Once a student has gotten used to recipes and ingredients using the staged 'next-ingredient' approach there's no reason to avoid conventional function headers. As an added bonus we can now: a) check that all 'reply' instructions in a recipe are consistent b) deduce what to reply without needing to say so everytime c) start thinking about type parameters for recipes (generic functions!)
* 2305Kartik K. Agaram2015-10-281-1/+1
|
* 2304Kartik K. Agaram2015-10-281-2/+2
| | | | | I no longer have any null types! That raises confidence that I'm on the right track.
* 2302 - restarting test_all_layers from a layerKartik K. Agaram2015-10-281-0/+1
|
* 2301 - test_all_layers fixesKartik K. Agaram2015-10-283-11/+11
|
* 2300 - remove callcc.mu from docs until it returnsKartik K. Agaram2015-10-282-54/+0
|
* 2299 - check types of ingredients in callsKartik K. Agaram2015-10-2812-64/+108
| | | | | | | | | | Still very incomplete: a) we perform the check at runtime b) tests for edit and sandbox apps no longer work; we can't fix them until we get type parameters in both containers and recipes (because list and list operations need to become generic).
* 2298Kartik K. Agaram2015-10-281-1/+1
|
* 2297Kartik K. Agaram2015-10-286-22/+27
|
* 2296 - record ingredient types on call stackKartik K. Agaram2015-10-282-0/+3
| | | | | As we perform type-checking earlier we'll delete these checks. But start with type-checking at run-time.
* 2295 - drop first-class recipes and continuationsKartik K. Agaram2015-10-287-380/+9
| | | | Making life too complex at this time.
* 2294Kartik K. Agaram2015-10-286-13/+35
| | | | Bah, sick of CALL and continuations.
* 2293Kartik K. Agaram2015-10-276-22/+43
|
* 2292Kartik K. Agaram2015-10-272-5/+5
|
* 2291 - parsing property treesKartik K. Agaram2015-10-273-9/+50
|
* 2290Kartik K. Agaram2015-10-271-10/+7
|
* 2289Kartik K. Agaram2015-10-271-11/+3
| | | | | | | | | | | | | | | | Now dilated reagent parsing is much simpler. We still can't parse nested hashes. We may never need that. For now the syntax model is: program = collection of top levels top-level contains a list of lines lines may be instructions instructions have reagents reagents can be in compressed or dilated syntax (or literal strings) property values inside reagents can be s-expression trees We balance {} inside top-levels, [] inside strings, and () inside property values.
* 2288Kartik K. Agaram2015-10-272-3/+6
| | | | | | | Make it easy to skip distracting valgrind errors when debugging more obvious errors in early layers. Just throw a 'test' at the end of build_and_test_until commands to not run valgrind (and make it a regular test run).
* 2287 - new lexing rulesKartik K. Agaram2015-10-271-5/+14
| | | | | Now we always consider words to be terminated at () and {}. We also always skip commas.
* 2286Kartik K. Agaram2015-10-273-3/+4
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-16 03:45:42 +0000