4 ms·
> although the tsc says it works, I always have a suspicion it could not work. Whereas with Java if it compiles it definitely works unless you have some R build
by mort96 6y ago
> although the tsc says it works, I always have a suspicion it could not work. Whereas with Java if it compiles it definitely works unless you have some R build issue
That's not true, right? AFAIK, the Java type system is broken and any type might silently be another type which doesn't support any of the methods the static type would indicate. It's basically as type safe as C in my eyes.
- mrkeen 6y agoIt's not that bad. Sure I'd call parts of it broken, but this isn't it: > any type might silently be another type which doesn't support any of the methods the static type would indicate When an object is typed differently from its actual runtime type, it's usually because it's hidden behind an interface type. So it indicates fewer methods than it supports. Safe, but unergonomic!
- twic 6y agoVariables being nullable is not "as type safe as C". Please don't waste people's time with hyperbole like this.
- mort96 6y agoI don't see why not? In Java, every access of an object variable can blow up your program even though the type checker is happy. In C, every access of a pointer variable can blow up your program. This seems very similar. Neither language provides type safety. EDIT: To be clear, Java is definitely safer than C. When Java "blows up" due to a null variable access, it throws an exception in a well-defined way. When C blows up due to a null pointer dereference, anything can happen, and if you're lucky your program terminates unconditionally. It's just that neither error is caught by the type system.
- selfhoster11 6y agoJava, if coded properly, ensures that a NullPointerException means that something went really, really wrong - in which case you're better off terminating than doing anything else. For variables that are expected to be missing occasionally, there are the Optional types or Collections/Lists, which I use extensively.
- kaba0 6y agoIt’s an exception not an error, you can easily catch that, which may make sense eg. when you run third party extensions that should not bring down your whole program.
- twic 6y agoIt's not just nulls. In C, you can compile and execute this without warning: int square(char* string) { int *number = (int*)(void*)string; return *number * *number; } It's UB, so in principle it can do anything, and in practice, the best thing it might do is return gibberish. The Java version of this would throw a ClassCastException on the first line.
- mort96 6y agoI already said Java is safer than C. But neither language would catch that error _in the typesystem_; it's a runtime error in both languages.
- kaba0 6y agoAnd `head []` will explode at runtime in Haskell. How is it relevant? Type systems can never prove every interesting property of a problem. Yeah, nulls suck, but there is very good static analysis for Java.
- mort96 6y agoThe point is that Java doesn't seem that much more type safe than C. I don't see how external static analysis tools are that relevant when we're talking about type safety.