Fridtjof Siebert

I ran into this while experimenting with #3690: The following results in an error ``` > ./build/bin/fz -e 'x ()->String := unit.as_string.substring 3; say x()' command line:1:32: error 1: Ambiguity...

This was brought up in #3737: `Type.as_string` causes an error, even though it can be interpreted as a type feature call: ``` > ./build/bin/fz -e "say Type.as_string" command line:1:5: error...

This is probably related to #3730. This code ``` x is f => say "x.f" type.f => say "x.type.f" Any.me => Any.this (id x).f x.me.f x.type.f ``` produces a strange...

AoC Issue: Missing implementation of `lteq` in type feature results in crash

1

This example does is missing an implementation of `test.x.type.lteq`: ``` test is a is h x := x type.q(a test.a.this) => a.h $FUZION/bin/fz part1_crash2.fz error 1: Found error clazz in...

See this small example ``` > ./build/bin/fz -e 'x => unit |> (exit 0)' command line:1:15: error 1: Ambiguity between direct and partially applied call target x => unit |>...

`id` called with two arguments results in wrong number of actual arguments

1

This is related to #3658, but maybe has a different root cause. This works ``` > ./build/bin/fz -e "s := id (Unary i32 (array i32)) sum; say (s

This code does not seem to be ambiguous since we have one actual argument ``` xyz is type.f(v i32) => f => bla => xyz.f 43 ``` but `fz` produces...

See this example which uses `i34` instead of `i32` ``` p is f(x i32) i32 => abstract q : p is redef f(x i34) => 42 ``` results in a...

`u128` works as expected with this small example: ``` > ./build/bin/fz -e "say (u128.one + u128.one)" 2 ``` `i128` does not: ``` > ./build/bin/fz -e "say (i128.one + i128.one)" $MODULE/i128.fz:28:8:...

See [this flang.dev](https://git.tokiwa.software/tokiwa/flang_dev/issues/344) issue. The docs for `base.fum`/`terminal.fum`/etc. should maybe be created separatedly and presented so in on fuzion-lang.dev, similar to Java APIs first giving a choice of modules, similar...