-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
fix contract caller types #2778
Conversation
Thanks Alex! Does this also address #1261 (comment)? If so, then do you mind adding some tests for that use case? |
Unfortunately, you still can't return a caller as a type from a function. That functionality is currently broken. I could fix that in a follow-on, but I think it will get fixed by introducing the |
This fixes some incorrect type unification and closes #1261. Really this was just the result of some behavior being untested, so it regressed over time. The type engine code for unifying contract callers had some typos.
I've disabled the
contract_caller_as_type
test, as this breaks that functionality, but that functionality is very much a special case and will be enabled by #2463 and a rework of theContract
type -- this should at least unblock the DAO contract and the berlin workshop.