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

call variant matching can sometimes report return type errors due to an error managing the return type info for parse-time variants #1928

Closed
davidnich opened this issue Jun 5, 2017 · 1 comment

Comments

@davidnich
Copy link
Contributor

No description provided.

@davidnich davidnich added this to the 0.8.12.10 milestone Jun 5, 2017
@davidnich davidnich self-assigned this Jun 5, 2017
davidnich added a commit that referenced this issue Jun 5, 2017
#1905

refs #1928 fixed a spurious exception raised due to incorrect management of the parse-time return value for callable objects with multiple variants with differing types
@davidnich
Copy link
Contributor Author

only happens when neither %strict-args nor %require-types is set

davidnich added a commit that referenced this issue Jun 6, 2017
…ata still

refs #1928 must ensure that return types are checked for consistency when committing variants at parse time
davidnich added a commit that referenced this issue Jun 6, 2017
@omusil24 omusil24 added the fixed label Jun 6, 2017
@omusil24 omusil24 closed this as completed Jun 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants