@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 ?
@RenewedRebecca @cwebber@octodon.social let them combine the best parts in a collaborative effort
@rml This looks like nominal vs structural "styles". Haskell clearly favors the former, but has a lot to work with the latter - Dynamic, Generics, all kinds of "Value" ASTs and coercing/parsing/building to bridge it.
I'm pessimistic, honestly, on the merits of generic structures throughout and usually want to parse them away and the boundary. Thus, it's Haskell for me (:
@rml hm... Perhaps I don't get what do you mean here. What's the difference between a composable and decomposable code?
@xkummerer @rml praxis
@rml how do you know it isn't the other way around?
@rml nah, theories compose quite badly
Toots as he pleases.