If we treat warnings as errors when merging to master we can afford to treat errors as warnings when running on a dev machine.
-
Show this thread
-
calling a function that expects an Int with a Maybe Int? Why not convert automatically treating Nothings as zeroes and print a warning every time we do so?
1 reply 0 retweets 0 likesShow this thread -
Yes we _never_ want to have this code in production but when the programmer just wants to know if his idea even works in the best case scenario there is no reason to add the friction of rejecting such things.
1 reply 0 retweets 1 likeShow this thread
When I implemented the tooling at my current workplace, this was how I thought about things, too. The central loop of programming is "does this idea work as I expect at runtime" and errors or warnings from type-checkers and linters are independent and secondary to this feedback.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.