brandon s allbery kf8nh
brandon s allbery kf8nh
Does it also fix the _no-project_ case, which fails the same way? #10684 looks like it's about using it inside a project.
As a reviewer, I would very much prefer smaller PRs. https://github.com/haskell/cabal/pull/9718 was a nightmare.
I'm not averse to following the proposals process, but would like to note that this has been an open issue for some time looking for someone to take it on:...
FWIW @ulysses4ever's observation about the TWG proposal WRT reviewing (which he'd also made on Matrix) is part of why I think a proposal is the wrong place for discussion of...
Part of the problem with GHC annotations is that GHC likes to arbitrarily change how it parses things. The realignment of parsing prefixes in (IIRC) 9.0 was intended to clean...
I think layout also complicates things: the AST for source using layout and source using explicit braces and semicolons should be the same, but the EPA will be totally different.
This still feels wrong to me. Do we also have to moot every other proposal accepted before the proposals process existed?
There also seems to be a conflict with the original intent. Solving all components together was intended to ensure that e.g. what you test is what you build; this is...
> Why does building library `A` requires it to also care about the whole huge dependency footprint of the `lens` library? That's not the issue. The issue is incompatibly solving...
The problem I described applies in either direction, not just under a hypothetical `B` depending on `B:foo`. The expectation in fact is `B:foo` depending on `B`, so ensuring that `B`...