Matt Parsons

I would *absolutely love* to have support for cross-package parallelism. That would make it much easier to break things into separate packages in our Large Work Repo without negatively harming...

Huh, that's surprising. I think I'd expect the naive approach to be something like: ```haskell type Dependencies = [Map PackageName DepInfo] getDependency :: PackageName -> Dependencies -> Maybe DepInfo getDependency...

> Overriding for constraints is certainly something we'd want. Overriding for source-repository-packages feels different to me. I think you're describing a difficulty in *implementing* this particular feature, rather than a...

I'm unable to replicate this on current `master` EDIT: forgive me, didn't recognize `aarch64` as not being what I was running 😅

I'd be happy to include the function. Even if we immediately throw a `WARNING` or `DEPRECATION` pragma and suggest something better, it's always good to have easily discoverable names that...

I'd be in favor of adding the `headMaybe` function to have API-parity with other collections (though, tbh, I'd much prefer for `head` to return a `Maybe Char`).

One irritating thing that i see a lot in Haddock is something like: ```haskell toLazyText :: Foo -> Text toStrictText :: Foo -> Text ``` An `LText` alias would be...

If we decide that deprecating the `Lazy` stuff is worthwhile then I'd be happy to write for the cause.

I talked to Snoyman about `Builder` and he suggested that it might be worth deprecating, as well. The gist of it is that a `Builder` type is almost always used...

Yeah, given the following modules: Foo Foo.Bar Baz Baz.Internal I'd expect the following: ``` exposed-modules: * -- other-modules: [] -- no other-modules clause -- expands to: exposed-modules: Foo Foo.Bar Baz...