Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Assigning a Builtin to Itself Leads to Panic #3933

Open
cyberthirst opened this issue Apr 10, 2024 · 0 comments
Open

Assigning a Builtin to Itself Leads to Panic #3933

cyberthirst opened this issue Apr 10, 2024 · 0 comments
Labels
bug - type 0 compiler halts or panics instead of generating code bug - typechecker issue with typechecker bug - UX a bug related to UX

Comments

@cyberthirst
Copy link
Collaborator

Version Information

  • vyper Version (output of vyper --version): commit 4b4e188ba83d28b5dd6ff66479e7448e5b925030

Issue description

Assigning some builtin to itself is not prevented and leads to a
compiler panic.

POC

For example, compiling the following code leads the compiler to raise
the following exception: CodegenPanic: unhandled exception , parse_Name.

@external
def foo():
    convert = convert

credits: @trocher

@charles-cooper charles-cooper added bug - UX a bug related to UX bug - typechecker issue with typechecker bug - type 0 compiler halts or panics instead of generating code labels Apr 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug - type 0 compiler halts or panics instead of generating code bug - typechecker issue with typechecker bug - UX a bug related to UX
Projects
None yet
Development

No branches or pull requests

2 participants