-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Shorten traces for TypeMismatch errors under -explain #18742
Conversation
This is a partial fix of scala#18737. We still can't explain the differences concisely, but at least we shorten the comparison traces by showing only steps that contributed to the overall failure and by avoiding repetitions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I wondered whether -Ydebug is the flag to use to unshorten and also whether we should be discarding the approx information. But I've come down with being happy with your choices there - and the rest is great to start with.
Also not sure about -debug. -verbose could be an alternate? I don't think the (approx) info is useful without further explanation, that's why I dropped it. |
Not sure - I end up not liking the result of any of them and just modifying the compiler. |
This is a partial fix for #18737. We still can't explain the differences concisely, but at least we shorten the comparison traces by showing only steps that contributed to the overall failure and by avoiding repetitions.