Things to check first
Feature description
Bring back check_argument_types and check_return_type.
There is quite a lot of code out there which uses check_argument_types and check_return_type and where authors do not want to update because they prefer the old API, or it's just too much effort to rewrite.
PaddlePaddle/PaddleSpeech#3056
espnet/espnet#5009
ExaWorks/psij-python#363
Also, one could argue, check_argument_types was simpler to use, it did not require a decorator. There could be reasons why you want to avoid using a decorator.
(I'm not sure if this feature request makes sense. I just want to raise awareness of the fact that a number of projects stick to old typeguard versions because of this. This is causing problems now for me because I want to use some of those projects (ESPnet) together with some own code which uses a new typeguard version, and this does not work now because of the incompatibility.)
Use case
Be able to update to newest version.
Things to check first
Feature description
Bring back
check_argument_typesandcheck_return_type.There is quite a lot of code out there which uses
check_argument_typesandcheck_return_typeand where authors do not want to update because they prefer the old API, or it's just too much effort to rewrite.PaddlePaddle/PaddleSpeech#3056
espnet/espnet#5009
ExaWorks/psij-python#363
Also, one could argue,
check_argument_typeswas simpler to use, it did not require a decorator. There could be reasons why you want to avoid using a decorator.(I'm not sure if this feature request makes sense. I just want to raise awareness of the fact that a number of projects stick to old typeguard versions because of this. This is causing problems now for me because I want to use some of those projects (ESPnet) together with some own code which uses a new typeguard version, and this does not work now because of the incompatibility.)
Use case
Be able to update to newest version.