James
James
Closes #366
This is a work-in-progress attempt at adding a `return` statement. In essence, it is the det dual of `fail`, causing a call to exit, but the call succeeds. Some things...
Some errors are reported without a position. An example can be found in the issue below. While an ideal patch would be to always have an error reported with a...
Ideally I'd use a resource to handle the parse string, but I found a few compile errors along the way regarding uninitialised temporary variables. I didn't get a change to...
A `readonly` type would be a type that, once a value of this type is defined, cannot be modified using any of the usual mutators defined automatically for a type....
Sometimes calling a foreign function can be a little clunky due to the repetitive nature of foreign calls. While this can be reduced by defining a Wybe "interface" as a...
Example: ``` pub type foo { foo(int, list(int)) } ``` The error produced is: ``` Error detected during type checking of module(s) test, test.foo Type error in call to =,...
As the title says. E.g., consider the following: ``` pub def list(ar:array(T)):list(T) = ls where { if { [?x | ?ar] = ar :: ?ls = list(ar) [x | ls]...
Once a resource is in scope it is always in scope for the current block. Adding an inverse `use` block (`disuse`, name tentative) would allow you to have a block...
If a test is called in a det context, the compilation will error. This is good, I hope we can agree. Sometimes, though, you don't really care about what happens...