Support for rich-loc & errorcode in parser & expansion errors
#2542
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.
Binding
rich-loc&errorcodein parser & expansion errorsAdded method of binding ErrorCode & rich location to parser and expansion errors.
Currently, the
Errorstruct only supports simple location toparserandexpansionerrors. Updated the code to handle all cases forerrorcodeandparsingerrors. Now, we can rich-loation toErrorstruct by using ampersand&operator.The
rust_error_atfunction immediately emits the error. But in some contexts we wish to collect them and discard them. Now, we can use errorcode and rich location inErrorstruct's context.gcc/rust/ChangeLog: