Content deleted Content added
JnRouvignac (talk | contribs) Tags: Mobile edit Mobile web edit Advanced mobile edit |
m →Benefits: Add how? for null safety |
||
Line 66:
It can also help language implementers provide implementations that execute dynamic languages faster by predicting the type of objects statically.<ref>{{cite web | url=http://blog.jooq.org/2014/12/11/the-inconvenient-truth-about-dynamic-vs-static-typing | title=The Inconvenient Truth About Dynamic vs. Static Typing | publisher=blog.jooq.org | date=11 December 2014 | accessdate=11 March 2016 | author=Lukas Eder}}</ref>
Finally, it increases [[type safety]] and can prevent problems due to [[null pointer]]s{{How|date=March 2020|title=The citation later is for the quote, flow sensitive typing doesn't seem to improve null-safety, a null-safe type system will. Possible confusion as these languages have nullable/non-nullable types, as checking null-safety through flow-sensitive typing generally equates to a null check without it}}, labeled by [[C.A.R. Hoare]]—the null reference inventor—as "the billion dollar mistake"<ref>{{cite web
|url=http://www.infoq.com/presentations/Null-References-The-Billion-Dollar-Mistake-Tony-Hoare
|title=Null References: The Billion Dollar Mistake
| |||