3 ms·
...I do spend some time looking for errors that the Haskell type checker would tell me about immediately. But what that means, is that I have to find my type er
by jcl 17y ago
...I do spend some time looking for errors that the Haskell type checker would tell me about immediately. But what that means, is that I have to find my type errors by thorough testing. Oh, wait a minute, I'm working with a testing tool! I actually find that the type errors are found very quickly by QuickCheck tests, so I need to write QuickCheck properties for testing, anyway, so that it's not as big a problem as I might have expected not to have the type checker.
I'm sure it's perfectly logical in context, but I find it amusing that he's writing a program that finds errors in itself.
- silentbicycle 17y agoThat's the point at which you know it works. :) I wrote a port of QuickCheck for Lua, and it caught a fencepost error in its own random value generation code. (The documentation is still pretty crappy, though - I need to rewrite that first.)