Re:SPy: An interpreter and compiler for a fast statically ty...
by setopt on Wednesday November 05, 2025 @08:30AM
(#45822617)
> A type is a contract, not a hint!
In Python it is a hint.
Re:SPy: An interpreter and compiler for a fast statically ty...
by rurban on Wednesday November 05, 2025 @08:40AM
(#45822709)
Exactly. That was their worst mistake ever
Re:SPy: An interpreter and compiler for a fast statically ty...
by setopt on Wednesday November 05, 2025 @02:28PM
(#45826813)
I agree. I use Beartype to get runtime type checks, but it shouldn’t be necessary. Some support for type checking, whether at byte compile time or runtime, should land upstream.
Re:SPy: An interpreter and compiler for a fast statically ty...
by almostgotcaught on Thursday November 06, 2025 @01:13AM
(#45832039)
Never gonna happen - the fundamental premise of the language is duck typing.
Re:SPy: An interpreter and compiler for a fast statically ty...
by setopt on Thursday November 06, 2025 @04:51AM
(#45833356)
Either you add type hints to your function and should expect it to be type checked, or you don’t add type hints and remain free to use duck typing as you want.
But not receiving as much as a warning when you violate type hints is the worst of both worlds.
Duck typing isn’t completely incompatible with type checking btw. Haskells type classes are an elegant solution to that, for example.
A type is a contract, not a hint!