News for hackers. Stuff that matters.

A comment on On Learning Rust and Go: Migrating Away from Python. Parent comment

Re:On Learning Rust and Go: Migrating Away from Python by oselhn on Sunday March 24, 2019 @11:02AM (#19476706)
Only if they are correct. I am pretty sure that in old code base it will not be correct unless automatically checked before commit.
[ Parent | on HN ]
Re:On Learning Rust and Go: Migrating Away from Python by coldtea on Sunday March 24, 2019 @11:16AM (#19476793)
That's trivially settled with a static type checker.

So the argument is analogous to saying "how can I trust the types in this Java program are correct, if it has never been compiled".

Well, whether some "old code base" has them correct or not, just run the type checker and find out.

[ Parent | on HN ]
Re:On Learning Rust and Go: Migrating Away from Python by oselhn on Sunday March 24, 2019 @11:32AM (#19476884)
If you do that you will probably hurt your productivity. There still will possible errors made by using 3rd party code.

In my opinion optional type checking is not comparable to statically typed language guaranties. So if I do not need types I would use python. If I need/want type specification I would use statically typed language.

[ Parent | on HN ]