John Ericson

Agreed combinators first is the right approach.

Can we start with stuff like this https://github.com/haskell/happy/pull/218 ? It is a clear improvement, and also no TH dependency. Not saying we should *never* do the TH, but in the...

Perhaps this should just be legal? An empty data type has not "committed" to having fields that are only positional. FWIW this is how rust does it, with: ```rust struct...

Well my point is that as a new user, ```haskell data Foo = Foo { a :: Int } f (Foo {..}) = 1 ``` being allowed, but ```haskell data...

Separately, while testing this out, I realized the "no fields" error message supersedes the "`RecordWildCards` is disabled" error message for this. That's a bug!

I opened language-change issue in https://github.com/ghc-proposals/ghc-proposals/issues/484

:) Glad it was persuasive! I will try to make it into an actual proposal soon. I agree it still needs a reword. > The data constructor 'LogOutView' does not...

Perfect! Yes "record structure" has those problem, but my first one felt a bit too verbose. "has unnamed fields" avoids both pitfalls!

https://github.com/ghc-proposals/ghc-proposals/pull/319 was supposed to solve this problem, among other things. Alas. Hopefully I can resurrect it after there is a new `-XNoIncomplete` to bolster its case.

I, as a more advanced user, might want to provide my own whitelist of extensions that are allowed to be suggested, or even so whitelist everything with a wildcard. For...