Autoharness: Don't panic on _
argument and add _autoharness
suffix to GOTO files
#3942
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.
Turns out that if an argument is just
_
, it doesn't havevar_debug_info
in StableMIR. So this PR changes autoharness behavior to provide_
for the argument name whenvar_debug_info
is None (instead of panicking).I don't currently know of any other cases where there wouldn't be
var_debug_info
, but we should pay extra attention to the cases where autoharness reports_
as an argument name and update this logic if need be.I also added an
_autoharness
suffix to the generated GOTO files so that it's easier to tell which files are from autoharness and which aren't.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.