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
Add first cut of style guide #263
Conversation
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.
Looks nice and clean to me so far 🌞 🌞
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.
Looks pretty good, just a few small comments, I actually made them a while ago but they weren't display because I hadn't submitted the review, sorry about that.
Perhaps we should add some |
I'm back from holidays so I'll be able to get back on this. :) |
Foo xs -> | ||
unlines xs | ||
Bar xs -> | ||
unlines xs |
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.
LambdaCase
has to be one of my favorite extensions, so much less noise here.
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.
Looks good, just the one comment about qualified imports
…erything that isn't the top level to be a second level heading.
* Added note about line length * Added section on module imports/declarations * Updated section regarding use of typeclass constraints * Added note about use of LambdaCase extension * Added section about requiring documentation for all public facing functions.
64114fe
to
a475c98
Compare
I mined a recent PR for most of these so fair to say there is plenty of adjustment required.
But it is easier to have this discussion here.