about summary refs log tree commit diff stats
path: root/032array.cc
Commit message (Collapse)AuthorAgeFilesLines
* 3221Kartik K. Agaram2016-08-181-3/+3
|
* 3209Kartik K. Agaram2016-08-171-1/+1
|
* 3120Kartik K. Agaram2016-07-211-6/+6
| | | | | | | | Always show instruction before any transforms in error messages. This is likely going to make some errors unclear because they *need* to show the original instruction. But if we don't have tests for those situations did they ever really work?
* 3119Kartik K. Agaram2016-07-211-1/+3
| | | | | | | Warn if 'put' or 'put-index' has a mismatch in the type of the product, not just the name. It won't do any harm, but could be misleading to a later reader. In both instructions, the product is just for documentation.
* 3110 - better support static arrays in containersKartik K. Agaram2016-07-111-1/+20
|
* 3064 - improve an error messageKartik K. Agaram2016-06-231-3/+3
|
* 3061Kartik K. Agaram2016-06-171-0/+1
|
* 3059Kartik K. Agaram2016-06-171-1/+11
|
* 2992Kartik K. Agaram2016-05-201-0/+14
| | | | | Raise an error if a 'put' or 'put-index' doesn't match ingredient and product. That wouldn't do what you would expect.
* 2990Kartik K. Agaram2016-05-201-15/+15
| | | | | | | | | | 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..
* 2932Kartik K. Agaram2016-05-061-1/+1
| | | | | | | More consistent labeling of waypoints. Use types only when you need to distinguish between function overloadings. Otherwise just use variable names unless it's truly not apparent what they are (like that the result is a recipe in "End Rewrite Instruction").
* 2931 - be explicit about making copiesKartik K. Agaram2016-05-061-14/+14
|
* 2899Kartik K. Agaram2016-05-041-1/+13
|
* 2898 - start filling in missing refcountsKartik K. Agaram2016-05-031-3/+5
| | | | | | | 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/+456
|
* 2863Kartik K. Agaram2016-04-241-467/+0
| | | | | Finally after much massaging, the 'address' and 'new' layers are adjacent.
* 2862Kartik K. Agaram2016-04-241-14/+0
| | | | | Layers 0-29 are now a complete rudimentary platform except for pointers and indirection.
* 2860 - rename 'index-address' to 'put-index'Kartik K. Agaram2016-04-231-45/+38
|
* 2847Kartik K. Agaram2016-04-201-4/+5
|
* 2846Kartik K. Agaram2016-04-201-4/+4
|
* 2831 - bugfix in static arraysKartik K. Agaram2016-04-131-10/+23
| | | | | | | | | | | I'd started using size_of() in transforms at some point, but not gotten around to actually updating it to support arrays before run-time. Wish there was a way I could statically enforce that something is only called at transform time vs runtime. Thanks Ella and Caleb Couch for finding this issue. Static arrays are likely still half-baked, but should get a thorough working-over in coming weeks.
* 2803Kartik K. Agaram2016-03-211-9/+9
| | | | | 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.
* 2735 - define recipes using 'def'Kartik K. Agaram2016-03-081-16/+16
| | | | | | | | | | | | 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.
* 2717 - bugfix for dilated reagentsKartik K. Agaram2016-02-261-0/+4
| | | | Make sure static arrays can take compound types.
* 2712Kartik K. Agaram2016-02-261-21/+21
|
* 2709Kartik K. Agaram2016-02-251-1/+0
| | | | | Only Hide_errors when strictly necessary. In other places let test failures directly show the unexpected error.
* 2707Kartik K. Agaram2016-02-251-1/+0
|
* 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-11/+11
| | | | | | | | | | | | | | | | | 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-2/+2
| | | | 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-2/+2
| | | | It's only for transient debugging.
* 2685Kartik K. Agaram2016-02-191-9/+9
| | | | | | | | | | | | | | | | 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.
* 2667 - redo container data structureKartik K. Agaram2016-02-171-8/+11
| | | | I've been gradually Greenspunning reagents. Just go all the way.
* 2660 - check dynamic arrays in exclusive containersKartik K. Agaram2016-02-151-11/+8
| | | | | Also a bugfix: don't cause future parse errors when these checks are triggered.
* 2658 - warn when containers contain arraysKartik K. Agaram2016-02-151-0/+32
| | | | | | | The rule is: a container type's size must be fixed. Arrays can violate this rule if the array length isn't included in the type. But we haven't been warning about this, and 'new' has been silently turning array elements to be empty.
* 2581 - make space for the refcount in address:sharedKartik K. Agaram2016-01-201-1/+2
| | | | | | | | | | | We don't yet actually maintain the refcount. That's next. Hardest part of this was debugging the assume-console scenarios in layer 85. That took some detailed manual diffing of traces (because the output of diff was no good). New tracing added in this commit add 8% to .traces LoC. Commented out trace() calls (used during debugging) make that 45%.
* 2576 - distinguish allocated addresses from othersKartik K. Agaram2016-01-191-3/+5
| | | | | | | | | | | | | | | | This is the one major refinement on the C programming model I'm planning to introduce in mu. Instead of Rust's menagerie of pointer types and static checking, I want to introduce just one new type, and use it to perform ref-counting at runtime. So far all we're doing is updating new's interface. The actual ref-counting implementation is next. One implication: I might sometimes need duplicate implementations for a recipe with allocated vs vanilla addresses of the same type. So far it seems I can get away with just always passing in allocated addresses; the situations when you want to pass an unallocated address to a recipe should be few and far between.
* 2555Kartik K. Agaram2016-01-111-2/+2
|
* 2475 - allow addresses to be converted to numbersKartik K. Agaram2015-11-271-2/+2
| | | | It's just the other direction we want to avoid.
* 2473 - bad idea to use /raw with multiple intentionsKartik K. Agaram2015-11-221-6/+6
| | | | | /raw is to express absolute addresses /unsafe is to sidestep type-checking in test setup
* 2459Kartik K. Agaram2015-11-181-0/+12
|
* 2450 - another pesky bugKartik K. Agaram2015-11-151-0/+12
|
* 2399 - consistent debug_string vocabularyKartik K. Agaram2015-11-081-2/+2
|
* 2377 - stop using operator[] in mapKartik K. Agaram2015-11-061-26/+26
| | | | | | | | | | | | | | | | 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.
* 2313Kartik K. Agaram2015-10-291-2/+2
|
* 2311Kartik K. Agaram2015-10-291-1/+1
|
* 2293Kartik K. Agaram2015-10-271-1/+1
|
* 2283 - represent each /property as a treeKartik K. Agaram2015-10-261-4/+4
|
* 2280Kartik K. Agaram2015-10-261-1/+1
|