@brion puckered asshole is a universal "password" character. You can't spell password without an ass.
@underlap @acowley found the discussion about that https://github.com/haskell/cabal/issues/7548
@underlap @acowley Anyway, how adding one more build tool would help?..
We've had `stack` already, with this specific mission of improving user experience. And improve it did. Now we have two concurrent build systems. Meanwhile, users continue to receive the `cabal install whatever` advice and hurt themselves with it.
@underlap @acowley Unless you happen to support Hackage and Stackage the result would be very niche, unusable in anything beyond perhaps online playgrounds. And then users would have to encounter "poor" experience of the real world anyway.
If only we had a library for Common Architecture for Building Applications and Libraries or something like that... ![]()
@zeux what's that? Nvidia fan service?
@sjb3d @aras @joeldevahl have you looked at dual contouring? It's more costly, with finding tangentials, but the result is as good as it gets.
@acowley So, this is -Wcompat? (=
To sum up, we have:
- Stackage LTS, pinning GHC major and a set of cross-compatible packages.
- -Wcompat for advance warnings.
- -XGHC2021 for baseline language features
- GHC proposal system to announce, plan ahead, and coordinate features.
What do we miss other than formal blessing that such-and-such GHC/LTS heralds a new "epoch"?
ghc/8.10.7 and its associated lts-18 appear to be something just like that.
And soon 9.6.x will come, that'll cement in GHC2021, text-2, etc etc
@acowley So, those are our stackage LTS snapshots? ![]()
@acowley If anything, it would be python 2/3 and scala 2/3, regularly.
Maybe I just prefer gradual fixing instead of "patch tues-years".
@acowley How it is better than 3-ghc-majors policy?
@wilfredh what about about emacs.zip ?
Toots as he pleases.