In 1ed3eaef2c71116ee6d06bfe0aaba03b238d1d70, I added an example file that is full of assertions. I plan to have more files like this to check other aspects of the language. We can check the assertions as follows:
This check should be automated. As a first step, maybe we can just add the call above to allTests.hs?
But a better solution would be to write a haskell function processFileAsTests :: FilePath -> Test that interpretes each assertion as a subtest, so that they are reported individually.
In 1ed3eaef2c71116ee6d06bfe0aaba03b238d1d70, I added an example file that is full of assertions. I plan to have more files like this to check other aspects of the language. We can check the assertions as follows:
This check should be automated. As a first step, maybe we can just add the call above to allTests.hs?
But a better solution would be to write a haskell function
processFileAsTests :: FilePath -> Test
that interpretes each assertion as a subtest, so that they are reported individually.