Taylor Fausak

:+1: I am strongly in favor of this proposal. I think it will allow all parties (Stackage, Hackage, Nix, and others) to continue improving independently without stepping on each other's...

For everyone wondering why Stackage might "fork" and introduce its own package namespace, it's answered in the first paragraph of the proposal: > Hackage has been extraordinarily successful as a...

This could come for free (or at least cheap) with https://github.com/purescript/pursuit/issues/139.

👍 This would be great to have!

For what it's worth, hindent is a full source formatter. One of the things I don't like about it is that it supports multiple styles. I think the main benefit...

[This line](https://github.com/archaeron/purescript/blob/d48008838fd80eef06090dcc391c717656bd1947/psc-format/Main.hs#L199) might need to change to make `psc-format` useful 😉

I just experienced exactly this confusion with the `GHC-54201` error code. Edit: This GHC issue seems related: https://gitlab.haskell.org/ghc/ghc/-/issues/23626

Oops, I meant to include a snippet showing `Cabal` being unable to parse that component name: ``` hs ghci> eitherParsec @UnqualComponentName "x1" Right (UnqualComponentName "x1") ghci> eitherParsec @UnqualComponentName "x-1" Left...

The (generic) package description parser appears to use a special parser for component names rather than using the `Parsec` instance. https://github.com/haskell/cabal/blob/00a2351789a460700a2567eb5ecc42cca0af913f/Cabal/src/Distribution/PackageDescription/Parsec.hs#L422-L423 https://github.com/haskell/cabal/blob/00a2351789a460700a2567eb5ecc42cca0af913f/Cabal/src/Distribution/PackageDescription/Parsec.hs#L389-L390 https://github.com/haskell/cabal/blob/00a2351789a460700a2567eb5ecc42cca0af913f/Cabal/src/Distribution/PackageDescription/Parsec.hs#L392-L405 That suggests you can use any `SecArgName`...

I bumped into this issue again. I think the intent is for component names to be the same as package names. This is enforced for library names, but not for...