Conversation
fisx
left a comment
There was a problem hiding this comment.
i have a change request, but i'll approve anyway in the hope that you'll follow it anyway before merging. if you disagree i'll find out how strongly i feel about this. :)
tools/stern/src/Stern/Intra.hs
Outdated
There was a problem hiding this comment.
I'm always surprised that there is no alternative to not . null
There was a problem hiding this comment.
Indeed. Also sounds like that's a hard naming problem. Any ideas?
There was a problem hiding this comment.
isJust . nonEmpty ? ;)
isJust . uncons ?
There was a problem hiding this comment.
How about isNotEmpty = not . null? Or to keep it consistent: notNull = not . null :D
smatting
left a comment
There was a problem hiding this comment.
+1 for keeping redundant $ and do. All the other changes look like an improvement to me.
Maybe apply hlint to more code to see more examples?
jschaul
left a comment
There was a problem hiding this comment.
Generally looks like good improvements. See in-line comments.
jschaul
left a comment
There was a problem hiding this comment.
So can we have a way to ignore enforcement of point-free style in .hlint?
Also @elland the changes here don't pass ormolu (linters step on CI); which suggests that your editor isn't set up to run ormolu on file save. You can manually run make format, but I'd suggest to hook ormolu into your editor setup. That's documented under /docs/developer somewhere.
|
Could we get the previously discussed and approved changeset (squash-) merged, and all follow-up changes made in a separate PR, please? It's very hard to review an ever-growing PR again and again. |
|
@jschaul I separated them per commits, so only the latest commit needs review, but I can break it down into PRs as well. |
In the interest of keeping things automated, consistent and avoiding repetition, we want to automate linting.
As it can be a contentious topic, this PR will serve as both a battleground for bikeshedding the linter rules as well as the de-facto linting process, whereas we incrementally apply the newly defined rules to the whole codebase.
Checklist