Fridtjof Siebert

For unsigned, this is part of the C standard, so I do not see any need to check this. But having such tests as part of the Fuzion tests for...

Here is a small example to reproduce the problem without changing the base lib: ``` String.mysubstring(from, to i32) String pre debug: 0

Updated the example ``` ex => seq(T type) ref is str(U type) ref : seq U is a U is abstract b(V type, c V) str V is ref :...

This is forbidden since this it is undefined in which order such fields should be initialized causing ambiguity as in file a.fz: ``` m1 := time.nano.read ``` file b.fz: ```...

We should have some mechanism to defer error handling, like Rust's `?.` operator. Your first case could be achieved using `bind`: ``` a option String := "hello" _ := a.bind...

Some of my earlier thoughts on this are [on the design pages](https://fuzion-lang.dev/design/matches_within_expressions)

Right, using an outer feature's name for an inner feature is probably not a good idea. However, we get similar problems when inheriting features that happen to have the same...

Yes, we will need this. Java's `Class.getResourceAsStream()` is another example. Would be good to get inspiration from other languages what API would be best for this. The way resources are...

I think the base module could still grow quite a bit, the module files are designed to be accessible efficiently even if large parts of the code are not used....

`comptime` is a loved feature of Zig, we should think about how such a feature would fit into Fuzion and what its semantics should be. An effect is only one...