-
Notifications
You must be signed in to change notification settings - Fork 15
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
Clean up more lint #10
Conversation
I'm happy with |
@@ -96,24 +96,24 @@ instance Monad m => IsString (m Doc) where | |||
-- horizontally if that fits the page. Otherwise they are aligned | |||
-- vertically. All comma separators are put in front of the | |||
-- elements. | |||
list :: (Monad m) => m [Doc] -> m Doc |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I prefer parentheses even for singleton constraints (so they don't have to get added when another constraint is added).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok I'll add those back and do the other changes.
So if we go through with this, the entire module is now incorrectly named! This is definitely a backwards breaking change as well. |
I'm happy with it still being named " |
How do you feel about using |
Sure, I'm happy with that. |
Ok I've pushed changes. I used |
I'm OK with a major version bump, especially as for anyone using a relatively recent version of GHC it's not going to be a problem (unless they were relying upon type coercion from the Monad constraint somehow). |
Some more changes that my linter (
hlint
) was complaining about but feel free to close if you're not a fan. I sort of wonder: do we really needMonad m
constraints in all these places? CouldApplicative
suffice?