@PLT_cheater@GabriellaG439 My extreme end take that I believe is at least partly true: The whole "quality vs speed" argument is something that was started by and is entirely peddled by corpo suits who want to maximise short term value and don't understand how maintenance or scaling a code base work.
@mattoflambda Of course, I'm not saying that this makes the situation great or even good - I am sharing what my experience and optimal strategy for ghc proposals is. (nor am I saying that we should do nothing about the situation, which has been going on for N years already)
@mattoflambda I believe the issue here stems almost entirely from one member of the community who is actively being overly aggressive/derailing on most forums where they engage in discussion, and that ignoring that individual produces better results and experiences.
@chrislpenner Most likely just so you don't lose progress. After all, it's not like you can usually retry the transaction to save if you've quit the game
@JadeMasterMath As far as I recall, this definition was necessary when talking about products of an infinite number of sets, and I haven't seen any other way to do this.
Is there some simpler alternative to this in classic FOL Set Theory?
@tomjaguarpaw @FlyingGuibou @kerckhove_ts@Iceland_jack In the DerivingVia paper, there's a section on deriving things via the Generic representation of a type, sounds like it might be what you're looking for. I think this is also what the Generically newtype wrapper is about, although not 100% sure
@ChShersh Thanks for the great work!
I consistently found myself enjoying the viewpoints and feedback you brought to proposals, as well as the compassionate ways in which you presented them/it!
I've started a discussion around adding a "Functor" HasField instance that would allow you to project records out of arbitrary Functors, e.g. data Struct = Struct {foo :: Int}; let mx :: Maybe Struct in (https://t.co/b9Tm5vPh4w :: Maybe Int)
Come join! https://t.co/2Vzkde3yZD
@ChShersh I would love for this to get more attention. I think it would save **so much** unnecessary churn with a very simple change. But we also need to make the hard call to not have the "duplicate imports" warning on by default, because otherwise -Wall users are still stuck by default.
This is a very small thing, but I just got my first ghc proposal implementation merged! It allows {..} syntax for nullary constructors, mostly to make writing TH manipulating records just a tad bit easier.
https://t.co/Y0rxrlk7cf