Closed dkellner closed 5 years ago
-1 from me. A goal of rio is to standardize existing best practices, and id
is well established in the Haskell ecosystem.
Likewise -1, and that's speaking from a position of dealing with a whole bunch of id
fields in business data. In practice, even in the presence of DuplicateRecordFields
, you're better off naming your accessors fooId
, barId
etc. for code clarity; and id
the function is so common in higher-order code that saving six characters is very much worthwhile.
As a beginner after trying Protolude I thought it's a nice idea to do this, i.e. considering the naming of id
historical cruft. Your answers made me actually grep through some code in Hackage and I can see what you're saying.
Thanks for being constructive! I close this to not clutter the issue list with a clear non-issue.
Cool, thanks!
What are your thoughts on renaming
id
toidentity
as Protolude does?From https://hackage.haskell.org/package/protolude: