Fridtjof Siebert
Fridtjof Siebert
A post condition in an abstract feature should be able to say something about the result: ``` test_post is f i32 post result > 0 => abstract ``` but this...
This test ``` test_infer_abstract_result is a is f => abstract b : a is redef f => 42 ``` should produce an error for `a.f` since no result type is...
See comment in #2904: 
This example passes `xyz.this` to the outside world in `xyz`'s preconditions ``` test_pre is R ref is hi unit => abstract hehe(x R) => x.hi; true xyz : R pre...
These two loops ``` > cat test_loop2.fz for i := 0, i+1 while i < 3 do say "hi" for i := 0, i+1 until i > 3 do say...
It might make sense to use effects to control resource usage of code, e.g., we could have effects like - **no heap allocation**: code is statically checked not to perform...
#2792 renamed one `String.type.concat` as `String.type.concat1` to avoid an error due to duplicate features since we would have three versions of the corresponding type features ``` concat(THIS#TYPE type) concat(THIS#TYPE type,...
``` > cat test.fz test is "{ for a := marray 100 false, a until (true) (1..2) |& (i -> !a[i])}" > ./build/bin/fz test java.lang.Error: check-condition failed! at dev.flang.util.ANY.check(ANY.java:371) at...
This used to be part of #2285: Since ranges of codepoints are frequently needed as in `codepoint.type.ascii_digits`, it might make sense to have `codepoint` inherit `has_interval`. But then,`has_interval` should no...
This small example ``` switch : choice unit is type.equality(a, b switch.this) => true a switch := unit _ := (concur.atomic a).read = a ``` should produce an error since...