about summary refs log tree commit diff stats
path: root/033exclusive_container.cc
Commit message (Collapse)AuthorAgeFilesLines
* 2990Kartik K. Agaram2016-05-201-9/+9
| | | | | | | | | | Standardize quotes around reagents in error messages. I'm still sure there's issues. For example, the messages when type-checking 'copy'. I'm not putting quotes around them because in layer 60 I end up creating dilated reagents, and then it's a bit much to have quotes and (two kinds of) brackets. But I'm sure I'm doing that somewhere..
* 2965 - update refcounts when copying containersKartik K. Agaram2016-05-151-3/+7
| | | | | | This is hopefully quite thorough. I handle nested containers, as well as exclusive containers that might contain addresses only when the tag has a specific value.
* 2955 - back to more refcount housekeepingKartik K. Agaram2016-05-121-3/+3
| | | | | Update refcounts of address elements when copying containers. Still lots to do; see todo list at end of 036refcount.cc.
* 2936Kartik K. Agaram2016-05-071-2/+2
|
* 2935Kartik K. Agaram2016-05-071-3/+3
|
* 2934 - all layers running againKartik K. Agaram2016-05-071-2/+0
| | | | | | Since I switched to a Mac laptop (commit 2725) I've been lax in running test_all_layers because I have to ssh into a server and whatnot. I should just get CI setup somewhere..
* 2931 - be explicit about making copiesKartik K. Agaram2016-05-061-13/+13
|
* 2898 - start filling in missing refcountsKartik K. Agaram2016-05-031-6/+7
| | | | | | | This commit covers instructions 'put', 'put-index' and 'maybe-convert'. Next up are the harder ones: 'copy' and 'merge'. In these cases there's a non-scalar being copied, and we need to figure out which locations within it need to update their refcount.
* 2893Kartik K. Agaram2016-05-031-0/+424
|
* 2863Kartik K. Agaram2016-04-241-414/+0
| | | | | Finally after much massaging, the 'address' and 'new' layers are adjacent.
* 2861 - 'maybe-convert' no longer returns addressKartik K. Agaram2016-04-231-13/+51
|
* 2818Kartik K. Agaram2016-03-281-2/+2
|
* 2803Kartik K. Agaram2016-03-211-6/+6
| | | | | Show more thorough information about instructions in the trace, but keep the original form in error messages.
* 2773 - switch to 'int'Kartik K. Agaram2016-03-131-8/+8
| | | | This should eradicate the issue of 2771.
* 2769 - fix build_and_test_until 043space.ccKartik K. Agaram2016-03-131-3/+3
|
* 2735 - define recipes using 'def'Kartik K. Agaram2016-03-081-13/+13
| | | | | | | | | | | | I'm dropping all mention of 'recipe' terminology from the Readme. That way I hope to avoid further bike-shedding discussions while I very slowly decide on the right terminology with my students. I could be smarter in my error messages and use 'recipe' when code uses it and 'function' otherwise. But what about other words like ingredient? It would all add complexity that I'm not yet sure is worthwhile. But I do want separate experiences for veteran programmers reading about Mu on github and for people learning programming using Mu.
* 2712Kartik K. Agaram2016-02-261-8/+8
|
* 2709Kartik K. Agaram2016-02-251-5/+0
| | | | | Only Hide_errors when strictly necessary. In other places let test failures directly show the unexpected error.
* 2704 - eradicate all mention of warnings from coreKartik K. Agaram2016-02-251-1/+1
|
* 2681 - drop reagent types from reagent propertiesKartik K. Agaram2016-02-211-4/+3
| | | | | | | | | | | | | | | | | All my attempts at staging this change failed with this humongous commit that took all day and involved debugging three monstrous bugs. Two of the bugs had to do with forgetting to check the type name in the implementation of shape-shifting recipes. Bug #2 in particular would cause core tests in layer 59 to fail -- only when I loaded up edit/! It got me to just hack directly on mu.cc until I figured out the cause (snapshot saved in mu.cc.modified). The problem turned out to be that I accidentally saved a type ingredient in the Type table during specialization. Now I know that that can be very bad. I've checked the traces for any stray type numbers (rather than names). I also found what might be a bug from last November (labeled TODO), but we'll verify after this commit.
* 2677Kartik K. Agaram2016-02-201-1/+1
| | | | Include type names in the type tree. Though we aren't using them yet.
* 2671 - never use debug_string() in tracesKartik K. Agaram2016-02-191-4/+4
| | | | It's only for transient debugging.
* 2685Kartik K. Agaram2016-02-191-4/+4
| | | | | | | | | | | | | | | | Stack of plans for cleaning up replace_type_ingredients() and a couple of other things, from main problem to subproblems: include type names in the type_tree rather than in the separate properties vector make type_tree and string_tree real cons cells, with separate leaf nodes redo the vocabulary for dumping various objects: do we really need to_string and debug_string? can we have a version with *all* information? can we have to_string not call debug_string? This commit nibbles at the edges of the final task, switching from member method syntax to global function like almost everything else. I'm mostly using methods just for STL in this project.
* 2679 - all tests passing againKartik K. Agaram2016-02-191-2/+3
| | | | | | | | | | Still not done, though: a) There's a few memory leaks to track down, including one in hash from 2668. b) replace_type_ingredients has gotten *even* uglier. I need to rethink it.
* 2667 - redo container data structureKartik K. Agaram2016-02-171-14/+6
| | | | I've been gradually Greenspunning reagents. Just go all the way.
* 2660 - check dynamic arrays in exclusive containersKartik K. Agaram2016-02-151-0/+17
| | | | | Also a bugfix: don't cause future parse errors when these checks are triggered.
* 2657 - type-checking for 'merge' instructionsKartik K. Agaram2016-02-151-0/+139
|
* 2655 - support shape-shifting exclusive containersKartik K. Agaram2016-02-141-2/+3
|
* 2653Kartik K. Agaram2016-02-141-10/+8
|
* 2635Kartik K. Agaram2016-02-061-0/+2
|
* 2582Kartik K. Agaram2016-01-201-2/+2
|
* 2580 - check product type of 'maybe-convert'Kartik K. Agaram2016-01-201-4/+46
| | | | I had to undo some over-zealous changes in 2576.
* 2555Kartik K. Agaram2016-01-111-3/+3
|
* 2378Kartik K. Agaram2015-11-061-1/+1
| | | | | | Now we're starting to run up against the misbehavior introduced by generics: Type tries to insert rows for type ingredients. That is a no-no.
* 2377 - stop using operator[] in mapKartik K. Agaram2015-11-061-16/+16
| | | | | | | | | | | | | | | | 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.
* 2311Kartik K. Agaram2015-10-291-1/+1
|
* 2284Kartik K. Agaram2015-10-261-5/+5
|
* 2277 - reagents now have a tree of typesKartik K. Agaram2015-10-251-12/+10
|
* 2270Kartik K. Agaram2015-10-121-1/+1
| | | | Thanks Caleb Couch.
* 2258 - separate warnings from errorsKartik K. Agaram2015-10-061-5/+5
| | | | | | | At the lowest level I'm reluctantly starting to see the need for errors that stop the program in its tracks. Only way to avoid memory corruption and security issues. But beyond that core I still want to be as lenient as possible at higher levels of abstraction.
* 2230Kartik K. Agaram2015-10-011-11/+17
|
* 2226 - standardize warning formatKartik K. Agaram2015-10-011-3/+3
| | | | | | | | Always show recipe name where error occurred. But don't show internal 'interactive' name for sandboxes, that's just confusing. What started out as warnings are now ossifying into errors that halt all execution. Is this how things went with C and Unix as well?
* 2115Kartik K. Agaram2015-08-301-0/+36
| | | | | Merging in unnecessary '0/empty' fields was a pain, and also made me do some additional debugging in the last commit.
* 1988 - handle reagents without typesKartik K. Agaram2015-08-131-2/+1
| | | | | | This can happen if 'canonize' fails. Make sure it doesn't kill mu. Thanks Caleb Couch.
* 1923Kartik K. Agaram2015-08-021-1/+1
| | | | | | | | | | Still iterating on the right way to handle incorrect number of ingredients. My first idea of creating null results doesn't really work once they're used in later instructions. Just add a warning at one place in the run loop, but otherwise only add products when there's something to save in them. Undoes some work around commit 1886.
* 1909 - clean up all null pointers of that ilkKartik K. Agaram2015-07-311-0/+4
|
* 1886 - gracefully handle malformed ingredientsKartik K. Agaram2015-07-291-1/+1
| | | | | | | | For example: x:number <- index y:address:array:number, 3 (forgetting to do a lookup) Thanks Caleb Couch.
* 1868 - start using naked literals everywhereKartik K. Agaram2015-07-281-12/+12
| | | | First step to reducing typing burden. Next step: inferring types.
* 1848 - core instructions now check for ingredientsKartik K. Agaram2015-07-251-10/+6
| | | | Also standardized warnings.
* 1844 - explicitly end each trace lineKartik K. Agaram2015-07-251-2/+2
| | | | | | | | | More verbose, but it saves trouble when debugging; there's never something you thought should be traced but just never came out the other end. Also got rid of fatal errors entirely. Everything's a warning now, and code after a warning isn't guaranteed to run.