The Future: It's So Bright It Burns the Eyes #292
leycec
announced in
Announcements
Replies: 2 comments
-
How to you plan to parse TypeVar stuff? Do you have a vague plan? Because it will require a sizeable change from current's beartype approach of verifying one argument at a time and you'll instead need to resolve them all at once, or am I mistaken? |
Beta Was this translation helpful? Give feedback.
0 replies
-
Ha-ah! It's my favourite numerical physicist, back with the hard-hitting questions that sting like a bee, float like a butterfly, and bite like a python. Let's take this to #236, where the painful Truth shall at last be revealed. 😮 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Welcome to @beartype's official roadmap for 2023—early 2024. The road ahead is patchy, filled with potholes, and probably not great for your suspension. This is that road:
beartype.claw
andbeartype.peps
subpackages at our ReadTheDocs (RTD)-hosted site.set[...]
,collections.abc.Set[...]
,typing.AbstractSet[...]
). Calling @langfield. If you even use Python anymore, curse you, Haskell! @beartype can help. If not, @beartype can bring you back.dict[...]
,collections.abc.Mapping[...]
,typing.MutableMapping[...]
). Calling @langfield even more.beartype.door.TypeHint
support for NumPy type hints. Calling @wesselb. This is your moment.collections.abc.Iterable[...]
,collections.abc.Collection[...]
). @langfield intensifies.TypeVar
-based type-stable parameter checking! Finally! At last! @beartype does something you want!tl;dr: It's gonna be awhile. See everybody in 2024.
</sigh>
Beta Was this translation helpful? Give feedback.
All reactions