-
Notifications
You must be signed in to change notification settings - Fork 0
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
Ergonomics #2
Comments
I have no idea why I posted this since it's not a question, and offers no solutions. The ergonomics of the |
It's a good thought. Let's keep it open. I am very interested to improve the ergonomic experience of this library. |
Regarding mapStrict :: (Strictly a, Strictly b) => (a -> b) -> Strict a -> Strict b
mapStrict f = strict . f . unstrict Regarding About instances, you're right. I can add them. Which would you like to be added? It won't work with See this commit for |
I added |
Hi, thanks for this library.
I was trying out the library and it seems to me that one advantage having parallel strict types has over wrapping with
Strict
is I can usefmap
on the strict types directly. If somebody likes the style of usingmaybe
orfmap
thenfromMaybe
instead of pattern-matching it feels a lot more awkward having to pattern match, then do those, then re-Strict afterwards.Another thing that doesn't come out of the box are instances like
Show
andEq
which makes me want to create orphan instances.It is nice that you can use the tuple syntax for strict tuples though.
Anyway those are my superficial thoughts.
The text was updated successfully, but these errors were encountered: