Fridtjof Siebert
Fridtjof Siebert
This is related to #2370 and #2251.
Thought about this a bit and came to the conclusion that the second case ``` > ./build//bin/fz -e 'f ()->unit := ()->say "hi"; say "hi"' ``` is ambiguous since it...
This is a variant of the [dangling else](https://en.wikipedia.org/wiki/Dangling_else) problem, which we also have and should solve similarly by producing an error.
the first case `f ()->unit := say "hi"; say "ho"` should be a sequence of two exprs, an assignment followed by the call `say "ho"`, it should print `ho` when...
The behavior in your example is surprising, but I think you can run into a similar surprise call `as_string` on a `Sequence`, maybe we should rename `as_string (one argument)`? I...
@simonvonhackewitz: I think this can be closed with #5536 basically solving that issue.
Missing argument types should definitely be forbidden, currently they should already cause an error unless there is a call to such a feature. As for result types: Yes, that would...
Few points from me - what features should our `tuple` type define, what properties should it implement? It would be convenient if, e.g., tuples would automatically be `equatable`, `orderable`, `hashable`,...
@simonvonhackewitz , can you collect what other languages (Go, Java, C#, Rust) use. I see that we have the following variants 1. with or without initial value 2. with a...
Having thought about this a bit, I suggest the following - instead of the `abort` result in reduce, we should have an `abort` effect that permits returning early from any...