-
-
Notifications
You must be signed in to change notification settings - Fork 388
Hlint more partial functions, and Debug.Trace #3000
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Hlint more partial functions, and Debug.Trace #3000
Conversation
Can we have global exceptions for |
Hmm, is eventlog tracing not exported from anywhere else? That's a shame. |
I'm not sure if I can do that easily, I might have to switch to explicitly listing the banned functions from |
I'm doing that, but in fact it doesn't let us get rid of any exceptions, since all of those modules also use non-eventlog tracing functions 🤷 |
756f7d0
to
e07a6fe
Compare
Maybe change those instances to use the existing log mechanism where it is easy? Perhaps a job for another time. |
Yep, once the ratchet exists it's a nice TODO list for anyone who feels like it :) |
Is there no way to ignore whole directories? For example the test suites seem like it would be ok to allow certain partial functions |
Not sure, I think it works off them module name anyway. I'm also not too bothered by it - the explicit list is not actually that long! |
Fair enough. Just looks tedious 😂 |
Turns out that for functions which are typically imported in multiple ways, you need to list both explicitly, and you can't combine them (see the linked HLint issue). So I did that and added some more exceptions.
I also banned
Debug.Trace
, removing a couple of dead usages and adding exceptions for the existing (!) usages.