Fridtjof Siebert

Here is a smaller example that causes this problem: ``` test is for a := 3 until true 1..2 | i -> a ```

But I see a new confusing error now: ``` > ./build/bin/fz test102.fz /home/fridi/fuzion/work/test102.fz:3:17: error 1: Ambiguous call targets found for call to 'a' (no arguments) 1..2 | i -> a...

Yes, this still needs to be checked, and probably forbidden. Since the outer feature of a type feature `o.f.type` is the type feature of the outer feature `o.type`, and we...

The type of a type is just `Type`: ``` > ./build/bin/fz -e "say (type_of 1)" Type of 'i32' > ./build/bin/fz -e "say (type_of (type_of 1))" Type of 'Type' > ./build/bin/fz...

Please do not create out-of-contexts issues. What did you do to create this message? What code did you run?

The explicit code to do this would be ``` e choice success end_of_file my_error := match d s success => s e end_of_file => e ``` is a little clumsy,...

The main question is where to add this syntax sugar. The precondition might be a nice place, i.e., find(x Sequence T) pre T : hasEquals T => (searchable_sequence T Sequence.this).index_of...

I think we should drop this, `(expr) arg1 arg2` should not be syntax sugar for `(expr).call arg1 arg2`.

Here is a smaller but similar example ``` > ./build/bin/fz -e 'b(b i32->i32) => say "{b 42}"' command line:1:26: error 1: Incompatible types when passing argument in a call b(b...

You call `p` and use `p` as a type in the type feature `ex.this.type.p.this.type.e`, so there is no surrounding `ex`. Extend your example as follows ``` ex(id i32) is p...