Matthew Lutze

Results 310 comments of Matthew Lutze

Meta Issue: Tracking the Future of the Flix Package Manager

> you write "prompt the user" in many places and i think excessive interaction can be impractical. init for example should just choose cwd but have an --folder xyz option...

List flatten on option

Traverse does not apply. And this does not spark joy: ``` List.filterMap(identity, list) ```

List flatten on option

> You should never construct a `List[Option[t]]` in the first place. Why do you have that? This code written by GitHub user @magnus-madsen does this: ``` /// ToString instance for...

List flatten on option

But yes, I agree, only a doofus would write something like that.

Keyword 'mod' in modulo

Hi, thanks for the report. Indeed we should change this (Flix previously had a keyword `mod`).

Inconsistent naming in the standard library

It would be really nice if we had some cool documentation comment feature that checked the parameters.

Import style

> > What about inner classes like `Map$Entry`? Should we rename these to `Entry` in the import? > > I suppose so. @mlutze Thoughts? I agree

Safety phase does not consider associated types when checking checked_cast

~~`Box[Int32]` is not the same as `Integer`. You should use `Integer.valueOf` if you need to create a Java `Integer` for some reason.~~

Safety phase does not consider associated types when checking checked_cast

> > `Box[Int32]` is not the same as `Integer`. You should use `Integer.valueOf` if you need to create a Java `Integer` for some reason. > > I am unsure actually....

fix: splitting the side-condition check in a T-Choose-* rule to increase performance.

Interesting, this change causes a failure in other tests.