about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* 2377 - stop using operator[] in mapKartik K. Agaram2015-11-0645-575/+593
| | | | | | | | | | | | | | | | I'm still seeing all sorts of failures in turning on layer 11 of edit/, so I'm backing away and nailing down every culprit I run into. First up: stop accidentally inserting empty objects into maps during lookups. Commands run: $ sed -i 's/\(Recipe_ordinal\|Recipe\|Type_ordinal\|Type\|Memory\)\[\([^]]*\)\] = \(.*\);/put(\1, \2, \3);/' 0[1-9]* $ vi 075scenario_console.cc # manually fix up Memory[Memory[CONSOLE]] $ sed -i 's/\(Memory\)\[\([^]]*\)\]/get_or_insert(\1, \2)/' 0[1-9]* $ sed -i 's/\(Recipe_ordinal\|Type_ordinal\)\[\([^]]*\)\]/get(\1, \2)/' 0[1-9]* $ sed -i 's/\(Recipe\|Type\)\[\([^]]*\)\]/get(\1, \2)/' 0[1-9]* Now mu dies pretty quickly because of all the places I try to lookup a missing value.
* 2376Kartik K. Agaram2015-11-051-7/+7
|
* 2375 - layer 9 doneKartik K. Agaram2015-11-051-6/+5
|
* 2374 - now edit works until layer 8Kartik K. Agaram2015-11-055-83/+73
|
* 2373 - bad bug: instruction was losing /lookupKartik K. Agaram2015-11-053-2/+18
|
* 2372Kartik K. Agaram2015-11-051-0/+4
|
* 2371 - layer 5 of editKartik K. Agaram2015-11-054-68/+45
|
* 2370 - layers 1-4 of edit are backKartik K. Agaram2015-11-055-357/+325
| | | | | | | | | | | | One nice consequence of all my deduction of reply ingredients is that I can insert the same fragment into recipes with different headers, and everything works as long as reply instructions are implicitly deduced. One thing I had to fix to make this work was to move reply-deduction out of rewrite rules and turn it into a first-class transform, so that it happens after tangling. I'm glad to see the back of that hack inside <scroll-down>.
* 2369 - layer 1 of edit is backKartik K. Agaram2015-11-052-34/+18
|
* 2368 - start getting edit working againKartik K. Agaram2015-11-052-23/+31
| | | | | Still seeing repeated null refinements. Maybe my approach to fixing those errors is fundamentally broken.
* 2367Kartik K. Agaram2015-11-051-1/+1
|
* 2366 - disallow static dispatch inside header-less recipesKartik K. Agaram2015-11-051-0/+1
| | | | | Not only can such recipes not have variants, their bodies too will be oblivious to multiple variants or generics.
* 2365Kartik K. Agaram2015-11-051-10/+10
|
* 2364Kartik K. Agaram2015-11-051-0/+10
|
* 2363 - duplex-list is now generic.Kartik K. Agaram2015-11-052-252/+252
| | | | It wasn't a phase-ordering issue after all..
* 2362Kartik K. Agaram2015-11-042-1/+2
| | | | | | Now we try to be smarter about checking for presence in the Type array. Still can't get generic duplex-list to work.
* 2361Kartik K. Agaram2015-11-041-1/+2
|
* 2360Kartik K. Agaram2015-11-0411-15/+60
| | | | | | | | | More flailing around trying to come up with the right phase ordering. I've tried to narrow down each transform's constraints wrt transforms in previous layers. One issue that keeps biting me is the Type map containing empty records because of stray [] operations. That's gotta be important.
* 2359Kartik K. Agaram2015-11-041-1/+1
|
* 2358 - starting to tackle the phase ordering problemKartik K. Agaram2015-11-0413-30/+32
| | | | | | | A new externality is starting to make its presence felt. Until I sort this out it's going to be hard to finish making duplex-list generic.
* 2357Kartik K. Agaram2015-11-041-1/+1
|
* 2356Kartik K. Agaram2015-11-041-8/+12
| | | | | I keep finding null property pointers and am fucking sick of wondering if it's because of this horseshit.
* 2355Kartik K. Agaram2015-11-041-0/+14
|
* 2354Kartik K. Agaram2015-11-042-3/+41
|
* 2353 - now 'list' type can be fully generic!Kartik K. Agaram2015-11-041-31/+34
|
* 2352Kartik K. Agaram2015-11-042-3/+4
|
* 2351 - support arbitrary type trees in 'new'Kartik K. Agaram2015-11-042-51/+77
| | | | In the process we also convert types to sizes before we start running.
* 2350Kartik K. Agaram2015-11-041-1/+7
| | | | Now it's not just tests that define recipe variants.
* 2349Kartik K. Agaram2015-11-021-19/+0
|
* 2348Kartik K. Agaram2015-11-021-5/+5
|
* 2347Kartik K. Agaram2015-11-021-0/+2
|
* 2346 - typoKartik K. Agaram2015-11-011-1/+1
| | | | No test, but discovered when fixing list.mu.
* 2345Kartik K. Agaram2015-11-011-2/+2
|
* 2344Kartik K. Agaram2015-11-011-0/+1
|
* 2343Kartik K. Agaram2015-11-011-0/+2
| | | | Clean up specialized recipes more thoroughly.
* 2342 - generalize generic recipesKartik K. Agaram2015-11-012-28/+108
| | | | | Support for type ingredients anywhere. I've been working on this since commit 2331.
* 2341 - fill in gaps in generic containersKartik K. Agaram2015-11-012-11/+61
|
* 2340Kartik K. Agaram2015-11-011-7/+5
|
* 2339 - don't let dump_types modify TypeKartik K. Agaram2015-11-012-3/+13
|
* 2338Kartik K. Agaram2015-11-011-12/+12
|
* 2337Kartik K. Agaram2015-11-011-0/+1
|
* 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.