about summary refs log tree commit diff stats
path: root/083scenario_screen_test.mu
Commit message (Collapse)AuthorAgeFilesLines
* 3937Kartik K. Agaram2017-06-221-0/+15
| | | | | Fix screen-checking functions to handle fake screen after scrolling. I can't believe I forgot about this during commit 3882.
* 3936Kartik K. Agaram2017-06-221-4/+4
|
* 3429 - standardize Mu scenariosKartik K. Agaram2016-09-281-8/+7
| | | | | | | | | | | | | A long-standing problem has been that I couldn't spread code across 'run' blocks because they were separate scopes, so I've ended up making them effectively comments. Running code inside a 'run' block is identical in every way to simply running the code directly. The 'run' block is merely a visual aid to separate setup from the component under test. In the process I've also standardized all Mu scenarios to always run in a local scope, and only use (raw) numeric addresses for values they want to check later.
* 3389Kartik K. Agaram2016-09-171-4/+4
|
* 3379Kartik K. Agaram2016-09-171-2/+2
| | | | Can't use type abbreviations inside 'memory-should-contain'.
* 3020 - names in chessboard testsKartik K. Agaram2016-05-261-4/+6
| | | | | | | | Extremely ugly change. Also ended up fixing some places where I was mixing up sources and sinks. But I'm not going to bother updating edit/ and sandbox/ apps. Just too many scenarios to clean up.
* 2864 - replace all address:shared with just addressKartik K. Agaram2016-04-241-4/+4
| | | | | | | Now that we no longer have non-shared addresses, we can just always track refcounts for all addresses. Phew!
* 2576 - distinguish allocated addresses from othersKartik K. Agaram2016-01-191-4/+4
| | | | | | | | | | | | | | | | 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.
* 2548 - teach 'print' to print integersKartik K. Agaram2015-12-281-2/+4
| | | | | | | | | | Still can't print non-integer numbers, so this is a bit hacky. The big consequence is that you can't print literal characters anymore because of our rules about how we pick which variant to statically dispatch to. You have to save to a character variable first. Maybe I can add an annotation to literals..
* 2468 - overload print-character as just 'print'Kartik K. Agaram2015-11-211-2/+2
|
* 2430 - make room for more transformsKartik K. Agaram2015-11-131-0/+29