Re:Python's “Disappointing” Superpowers
by ReflectedImage on Wednesday February 01, 2023 @05:29PM
(#34618905)
No programming language tells you if a program is correct at compile time. Type errors aren't a very common type of bug either.
[ Parent
| on HN ]
Re:Python's “Disappointing” Superpowers
by kayodelycaon on Wednesday February 01, 2023 @06:07PM
(#34619409)
The most common type error I see are unexpected null values. Which, surprise, is still a problem in many typed languages. :)
Re:Python's “Disappointing” Superpowers
by bobbylarrybobby on Wednesday February 01, 2023 @08:19PM
(#34620727)
“No programming language tells you if a program is correct at compile time” is technically true, but my experience is that about 99% of the refactors I do in rust, no matter how large, go back to working correctly as soon as the code compiles again. I don't think anything like this is possible in a language like python.
Re:Python's “Disappointing” Superpowers
by necovek on Saturday February 11, 2023 @04:06PM
(#34756350)
That's true, but mostly because one rarely compiles Python.
I've done significant refactors in untyped Python without much ado: as soon as your tests pass, code works too. I've done significant changes with tests passing on the first go.
As I know, SPARK can do this (in particular, thanks to the strong type system).
https://learn.adacore.com/courses/intro-to-spark/chapters/01...