David Pearce
David Pearce
Hey, Yeah, so that second obligation is interesting. I'll have to have a think, but yeah definitely one of these two makes sense.
Realistically, need to regenerate these tests using `jmodelgen`
This is also causing me problems moving between different instances of `dom::Element`
Another example arises in `AmbiguousCoercionCheck` and test `TypeEquals_Invalid_7`: ```Whiley function f(int|null x) -> (bool|null r): // if x is int && x >= 0: return false else: return x ```...
What is the format? Its an `@` followed by an identifier that represents a type name which is resolved in the usual fashion for types, and which may be followed...
There are three supports value formats: * **Primitives** ``` @test(0) ``` * **Records** ``` @test{field: 1} ``` * **Arrays** ``` @test[1,2,3] ```
I did manage to workaround this with a `property`: ```Whiley property unchanged2({int data, null|List next} node) // My data is unchanged where node.data == old(node.data) // Everything else is also...
In addition, there are problems related to field and array accesses (and possibly others). As an example, consider this: ```Whiley method f(int[][] xs) : // int[] ys = xs[0] ys[0]...
This article is worth a read on the subject: https://futhark-lang.org/blog/2017-10-10-block-comments-are-a-bad-idea.html
Minimal example: ```Whiley import std::option with Option method main() -> Option: return option::Some{value:0} ```