Common errors such as typos and argument errors can be caught by the type checker.
Confidence: Since an incorrect program won’t pass type checking, developers can refactor with more confidence. Employing a type checker can help you find bugs during development and prevent those bugs from going to production. Correctness: Type checking, like testing, is a way to be confident that your codebase is functioning properly. Optional, gradual type systems have been introduced to Python and JavaScript and they’re big successes. Programmers have experienced excellent type systems in other languages, and want those benefits in Ruby. At Ruby’s inception, there were no 10-year-old Rails apps which people struggled to maintain, only greenfield Ruby scripts for toy projects. Large, sprawling projects are becoming more common. 
So why is there so much interest in adding types to Ruby? Part of Ruby’s appeal is to be free of the cruft of its predecessors. So let’s take a look: what’s the big deal, and what have they been up to? Why Type Check? This fall, several people presented their work on Ruby type checkers.
0 kommentar(er)
