-
Notifications
You must be signed in to change notification settings - Fork 90
Record instances #207
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Not necessarily more garbage since builders will allocate closures (as opposed to new records). I think it's mainly that |
There is a reason for not including EuclideanRing and DivisionRing: there’s no clear way of defining division when you have more than one field in the record. What should |
I think a Bounded instance makes sense, given that we already give records Ord instances. |
Thank you both for your answers 🙇 I added a |
Are
Semigroup
,Monoid
,Semiring
andRing
instances for records usingRecord.Unsafe.unsafeSet
on purpose instead of composing a bunch of record builders? Don’t that yield a lot more garbage?Also is there a reason for not having records instances of
Bounded
,EuclideanRing
andDivisionRing
?The text was updated successfully, but these errors were encountered: