4 ms·
Do you mean decorators? A solution like that exists and has been used for a while. It really is only usable for run-time type-checks. See here: https://github.c
by justusw 11y ago
Do you mean decorators? A solution like that exists and has been used for a while. It really is only usable for run-time type-checks. See here: https://github.com/dobarkod/typedecorator https://github.com/dobarkod/typedecorator
With type annotations you can have static guarantees, which decorators will not be able to provide, as decorator methods will be called and resolved only during runtime. Objects imported from `types` hopefully will not.
- hardwaresofton 11y agoYeah, that's what I meant to type, thanks. https://github.com/dobarkod/typedecorator https://github.com/dobarkod/typedecorator is interesting -- I was imagining type signatures more like haskell's: addNumber :: Int -> Int -> Int translating to something like @TypeSignature([int, int, int]) def add_number(a,b): .... It's just as possible to have the compile-time program that's doing the checking process the decorators.