Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In working on a Chapel program recently, I ran into a situation where I was having trouble seeing why a particular candidate didn't resolve for a call. Today, we describe the detailed reason for a call failure when printing the first candidate. But, the candidate I was expecting to match was a later candidate, and so the details weren't printed out. I was able to work around this issue and find the problem. However, it would have been easier if I had a way to ask the compiler to describe all of the candidates.
This PR adds a flag,
--describe-candidates
, that asks the compiler to print the detailed reason for a call failure when printing any candidate.note: and 2 other candidates, use --print-all-candidates to see them