Re:Effective Programs: 10 Years of Clojure
by pyrale on Tuesday October 31, 2017 @06:23PM
(#15597120)
Using a static type checker means that an error doesn't creep across all my code. The worst case you describe pretty much never happens, and the smaller instances I get are reified to a generic form I am trained to analyze and solve quickly.
> Your analogy doesn't apply.
One would think I am well placed to describe my own experience of interacting with a type system.
Re:Effective Programs: 10 Years of Clojure
by wellpast on Tuesday October 31, 2017 @06:10PM
(#15597030)
The worst case for the number of places I have to go fix is O(n). I.e., the verification half is O(n). The solution search side ("solving the puzzle") may be worse, because I have to generate/find the code that fits the type checker.
Your analogy doesn't apply.
I can read a book in O(n) time, where n is the number of words in the book. I can read a single word in O(1) time.
When I get a type error, that is not a O(1) fix. The type error is connected to my program in the large and I have to understand/process more than just the single line where the error is called out. The worst case, obviously, is O(n).