Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
This commit resolves a critical low-level issue in @beartype's dynamic type-checking code generator for **nested beartype validator-in-container type hints** (e.g., type hints of the form `list[typing.Annotated[{type}, Is[{validator}]]]`), resolving issue #372 kindly submitted by @ArneBachmann, fearless author of the peerless programming language [AWFUL (Arguably Worst F*cked-Up Language)](https://github.com/ArneBachmann/awful), which @leycec is promptly going to port the @beartype codebase to. Press F to doubt. The accursed @beartype 0.18.X release cycle continues to bedevil our world. (*Inchoate incoherence is the GOAT!*)
- Loading branch information
Showing
6 changed files
with
315 additions
and
146 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
7e9eef4
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh no, please don't advertise AWFUL... It was a fun project, but the big test case fails in an undebuggable way, so it was never finished in good shape :-(
I never learned how to write parsers and compilers, so this was a struggle. But I like how all the little features play together in an interesting way :-D
7e9eef4
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm so sorry. I fell in love with the AWFUL acronym – and the rest was history. I couldn't help myself! 😄
I know your pain, though. I have the exact same mixed feelings about a language I too made years ago when I had youthful hair:
zeshy
, azsh
-based shell scripting language so painfully broken I shudder to link anyone to it. Unlike AWFUL,zeshy
didn't even have unit tests. It was the manifest failure ofzeshy
(and all my hopes and dreams of being awesome with it) that inspired me to go hard on automated QA devtools like @beartype – and the rest was history.Thank the GitHub Gods for
zeshy
! For it has given us @beartype.