3 ms·
The problem is in tooling. If all compilers/builders out there could detech null for us, those kinds of error could be taken care with much more ease.
by revskill 8y ago
The problem is in tooling.
If all compilers/builders out there could detech null for us, those kinds of error could be taken care with much more ease.
- rusk 8y agoA lot of static analysis tools will do this. I can't speak for other IDEs, but Intellij will always warn me if I'm exposing myself to some NULL operations. I do think better first class language support is the way to go though.
- giornogiovanna 8y agoTypeScript can be easily configured to do this[0], and Kotlin always does this[1]. The future is now! [0]: https://www.typescriptlang.org/docs/handbook/release-notes/typescript-2-0.html https://www.typescriptlang.org/docs/handbook/release-notes/t... [1]: https://kotlinlang.org/docs/reference/null-safety.html https://kotlinlang.org/docs/reference/null-safety.html
- ozim 8y agoIn VS with resharper I get "Possible null exception" as warning, but null exception is runtime thing and not compile time, so I don't see how it is tooling problem. Compiler does not know your user did not fill in some field in form.
- empath75 8y agoA higher level programming language is a kind of tooling. Use a language that doesn't have NULL and problem solved.