Re: Request for feedback: deriving strategies syntax

I haven't followed the thread but do we actually need a name for it, can't it be indicated by omission? ‘default’ or ‘builtin’ sounds okay 2016-08-18 20:00 GMT+00:00 Nicolas Frisby :

The Report specifies the semantics of most (all other than Generic?) derivation strategies that are baked-in to the compiler.

https://www.haskell.org/onlinereport/haskell2010/ haskellch11.html#x18-18200011

I think this raises an issue of what *exactly* we are currently referring to as "bespoke". E.G. can it vary with the precise compiler being used? (Maybe your wiki page addresses this; I haven't clicked through.)

But maybe "language-report" would supplant "bespoke". And perhaps "GHC-7.8" would also make sense, if the baked-in derivation scheme varies from the report's spec? Etc.

HTH. -Nick

On Thu, Aug 18, 2016, 12:24 Elliot Cameron wrote:

...

Given the prevalence of spellings like "normalise" in common Haskell packages, we might just be settling on British English. Being American makes that a tad difficult on my end, but personally I can make peace with it.

On Thu, Aug 18, 2016 at 3:19 PM, Matthew Pickering < matthewtpickering@gmail.com> wrote:

...

I also like 'bespoke' but then it seems to be a much more common in British English than American English.

On Thu, Aug 18, 2016 at 7:46 PM, Ryan Scott wrote:

...

Bardur,

Since you don't like "bespoke", would you mind suggesting an alternative, or advocating for a previously mentioned idea? From [1], the ideas I've seen tossed around are:

* builtin * standard (Elliot Cameron suggested it here [2]) * wiredin (Cater Schonwald suggested it here [3]) * magic (Andres Löh suggested it here [4]) * native * original * specialized (the above three are ad hoc suggestions I came up with in a hurry)

Ryan S. ----- [1] https://ghc.haskell.org/trac/ghc/wiki/Commentary/Compiler/ DerivingStrategies#Alternativesyntax [2] https://mail.haskell.org/pipermail/ghc-devs/2016-July/012448.html [3] https://mail.haskell.org/pipermail/ghc-devs/2016-July/012450.html [4] https://mail.haskell.org/pipermail/ghc-devs/2016-July/012453.html _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

---

ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs