-
Notifications
You must be signed in to change notification settings - Fork 2.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
Improve error messages on failed control-flow transpilation #9049
Conversation
As part of this, it became convenient for the `Error` transpiler pass to be able to accept an arbitrary `property_set -> str` callable function to generate the message, rather than just relying on fixed formatting strings.
Thank you for opening a new pull request. Before your PR can be merged it will first need to pass continuous integration tests and be reviewed. Sometimes the review process can be slow, so please be patient. While you're waiting, please feel free to review other open PRs. While only a subset of people are authorized to approve pull requests for merging, everyone is encouraged to review open pull requests. Doing reviews helps reduce the burden on the core team and helps make the project's code better for everyone. One or more of the the following people are requested to review this:
|
Pull Request Test Coverage Report for Build 4568419805
💛 - Coveralls |
Summary
As part of this, it became convenient for the
Error
transpiler pass to be able to accept an arbitraryproperty_set -> str
callable function to generate the message, rather than just relying on fixed formatting strings.Details and comments
Fix #8921.
The new handling in the
Error
transpiler pass technically makes this ineligible for backporting, as it's a new feature in a technically public class (albeit not one I think anyone else will necessarily be using). I could make this change stable by making the error message worse, or potentially temporarily making a new internalError
pass purely for this use-case.