Jonathan Lindegaard Starup
Jonathan Lindegaard Starup
I think here it is done on purpose - I'd rewrite it with `.take` on both sides
> Or maybe its because [#10532](https://github.com/flix/flix/pull/10532) is not in yet? Yes, this program is observing the unsoundness that arity will fix Short explanation for @CasperDN, you can confuse the compiler...
I've changed it to feat since it is a feature and ready to review since the code is done
> What is the interaction with mutable local variables, and We don't have mutable variables. It interacts with structs/ref/array like everything else does > Why can this not just be...
@magnus-madsen sorry im a bit late to this party, is there still things left to answer?
Right now `Option[t] {case None case Some(t)` gets monomorphed into nothing essentially (`Some(42)` becomes `("Some", 42)` ish). We should we do for structs? - We can monomorph them into combinatorial...
New plan for monomorphization - flatten everything to a `Struct` type with a list of values it holds The insight was that no construct needs to know the name of...
@dghosef this is outdated right?
`Flix.Object`?
shouldnt we just allow base effects to leak into the entrypoint and then add the default handlers there?