about summary refs log tree commit diff stats
path: root/022boolean.cc
Commit message (Collapse)AuthorAgeFilesLines
* 1962Kartik K. Agaram2015-08-091-4/+4
| | | | Standardize test names.
* 1953 - more warningsKartik K. Agaram2015-08-071-3/+12
|
* 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-1/+1
| | | | Also standardized warnings.
* 1702 - experiment: start using 'ordinal' in namesKartik K. Agaram2015-07-041-3/+3
| | | | | | | It comes up pretty early in the codebase, but hopefully won't come up in the mu level until we get to higher-order recipes. Potentially intimidating name, but such prime real estate with no confusing overloadings in other projects!
* 1414 - traces now robust to new recipes/typesKartik K. Agaram2015-05-211-16/+0
|
* 1391 - avoid unsigned integersKartik K. Agaram2015-05-171-6/+6
|
* 1366Kartik K. Agaram2015-05-141-3/+3
|
* 1357 - temporarily revert floating-point supportKartik K. Agaram2015-05-121-3/+3
|
* 1356 - snapshot #2: floating point supportKartik K. Agaram2015-05-121-3/+3
| | | | | | | | | | | | | | | I added one test to check that divide can return a float, then hacked at the rippling failures across the entire entire codebase until all tests pass. Now I need to look at the changes I made and see if there's a system to them, identify other places that I missed, and figure out the best way to cover all cases. I also need to show real rather than encoded values in the traces, but I can't use value() inside reagent methods because of the name clash with the member variable. So let's take a snapshot before we attempt any refactoring. This was non-trivial to get right. Even if I convince myself that I've gotten it right, I might back this all out if I can't easily *persuade others* that I've gotten it right.
* 1298 - better ingredient/product handlingKartik K. Agaram2015-05-071-38/+74
| | | | | | | | | | | | | | | | | | | All primitives now always write to all their products. If a product is not used that's fine, but if an instruction seems to expect too many products mu will complain. In the process, many primitives can operate on more than two ingredients where it seems intuitive. You can add or divide more than two numbers together, copy or negate multiple corresponding locations, etc. There's one remaining bit of ugliness. Some instructions like get/get-address, index/index-address, wait-for-location, these can unnecessarily load values from memory when they don't need to. Useful vim commands: %s/ingredients\[\([^\]]*\)\]/ingredients.at(\1)/gc %s/products\[\([^\]]*\)\]/products.at(\1)/gc .,$s/\[\(.\)]/.at(\1)/gc
* 1276 - make C++ version the defaultKartik K. Agaram2015-05-051-0/+94
I've tried to update the Readme, but there are at least a couple of issues.