-
Notifications
You must be signed in to change notification settings - Fork 670
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
Revert "Notations: Trying using a notation with or w/o removal of coe… #11053
Conversation
…rcions." This reverts commit 688859b.
This bug affects 8.10 too, if a new point release is to be made @vbgl can consider backporting this |
Can you please add a test-case corresponding to the bug report? Thanks. |
There you are, this is the test I've used for bisecting (plus |
@gares, thanks for the quick finding of the issue! If it is clear that #8890 is a change of semantics, I would not say that it is bug though, especially regarding this other expectation. Since this is already released in 8.10, I'd be tempted to test the following cheap-to-implement improvement of the criterion used in #8890: look for notations which span the full application of the coercion to a term, rather than looking for a notation which applies to any partial prefix of the term as it is with #8890. By doing so, in the #11033 example, |
I would prefer this solution over simply reverting #8890 |
Superseeded by #11090 |
Fix #11033
Or course any other fix is fine to me