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
Improvements to -Vimplicits
; errors now show complete implicit search tree
#9944
Conversation
@tribbloid interested in returning to this? |
Of course. I'm just fixing a bug for splain 1.0 |
2461e39
to
a7220ae
Compare
@tribbloid interested in returning to this? |
Yes, don't want to drag it any longer, it will be 2.13.11 or monastery |
a7220ae
to
b99c1f9
Compare
I hear that a choice cell just opened up at the monastery ;-) |
NOOOO you can't just drag me in without me submitting it! Seriously when will be the feature freeze date? I'll just need a week to wrap it up, with all test cases |
we're not exactly sure. it's not imminent. but we're coming up on the 4 month mark since 2.13.10, and it would be highly unusual of us to let more than 6 months pass, so... you're safe for at least 2 or 3 weeks, say. after that, can't predict. |
b99c1f9
to
4b3c5c2
Compare
Backport almost finished and passed partest locally. Let's wait for the CI Still, this doesn't rule out the monastery as there may be numerous problems in downstream testing, format compliance & release schedule. |
(CI likes the last commit, but you'll need to rebase such that every commit passes — that's the "combined" check.) |
5362cc3
to
37bb980
Compare
…on par with splain 1.0.0
37bb980
to
7117ee4
Compare
Sorry for being slow, Travis CI is getting a bit squishy, got "504 Gateway Time-out" in my last run. |
Don't worry about the Travis-CI failure — it's unrelated to your changes. I've opened scala/scala-dev#832 on it Let us know if you consider this ready for review |
thanks a lot! Will remove "Draft" tag once I'm comfortable |
Finished reviewing, the only issue left is formatting difference. Is there a formatter configuration I could use to enforce it automatically? |
…on par with splain 1.0.0
7117ee4
to
cb6b3a1
Compare
We don't have a repo-wide style, no. We try to match a file's existing style when tweaking existing code, prioritizing minimal/reviewable diffs. But if you're really tearing something up you can suit yourself as long as it's within the (admittedly nebulous) boundaries of common, consensus style. |
Oh, one thing we'll want before merge is to have the PR title and description be your best effort at documenting these changes from the user's point of view. |
-VImplicits
now show complete implicit search tree
…now show complete implicit search tree
cb6b3a1
to
6573972
Compare
I believe it has been done. @SethTisue Can we start the review if it is up to your standard? |
This patch only synchronise behaviour & test cases of all features of splain-plugin before 1.x. New features are not included |
-VImplicits
now show complete implicit search tree-Vimplicits
; errors now show complete implicit search tree
I revised the PR title and description a bit further, but I think the PR description could use further work, both for reviewers and for end users. Can you expand it to show an example of the improved behavior? "Suppose we're debugging the following error. The following implicit search tree is now produced, and it shows that the problem is X", something like that maybe? |
sounds good, updated |
Any plan to integrate it before the deadline? |
I don't anticipate any trouble with this making 2.13.11 |
thank you! |
Backports bugfixes from splain 0.5.8 & 1.0.0
The new algorithm now build a tree instead of an indented list that records implicit search process. As a result, implicit terms being considered multiple times in a search will be displayed repeatedly.
E.g. for the following scala code:
The old error message can only show term
i6b
once, this is problematic asi6b: I6
was summoned for multiplep: I6
arguments:after this patch, the error message becomes:
which shows multiple summoning attempts of
i6b
correctly