Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
While sets are not ordered, type signatures need list items in a specific order, or the type checker will complain.
Eg, Set '[Natural 0, Natural 1] vs Set '[Natural 1, Natural 0]
Your examples suggest to leave off the type signatures and let them be inferred, sidestepping this problem. Which is fine, but in my application, the content of the set is important documentation, so I'd rather include type signatures.
I don't know if this is fixable with current ghc's Data.Type.Equality
Hi! Yes, the examples tend to rely on inferring the types, but you can use the