4 ms·
Is it a waste to keep the test around until you're ready to switch to a more sophisticated type system?
by ben0x539 7y ago
Is it a waste to keep the test around until you're ready to switch to a more sophisticated type system?
- pojzon 7y agoA question, coz Im not sure I follow. How is type system (as described by wiki) supposed to test domain or functionality? Or are you talking here about completely different type system ?
- ben0x539 7y agoWhat you can do with the type system depends on the language. It can't replace tests entirely, but it can usually make some more boring tests superfluous, and in more exotic languages the type system can be surprisingly helpful.
- chongli 7y agoIt adds to the technical debt of the project. Some teams may never decide they're "ready" for a more sophisticated type system. That's fine, but they're still on the hook for maintaining those test suites which might pose significant roadblocks to refactoring or rewriting parts of the system.
- iso-8859-1 7y agoYou can prove a merge sort correct with dependent types. However, a typed implementation of merge sort will arguably be more difficult to mold into a TimSort if it isn't dependently typed. What you say?
- chongli 7y agoI don't have any experience with dependently typed languages. I hope (schedule permitting) to take a course in dependently typed programming (using Agda) and formal verification in the fall. I'll have much more to say on the topic after completing the course.