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
Add error emitting when we can't resolve id expr #2895
Add error emitting when we can't resolve id expr #2895
Conversation
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.
thanks :D
else { | ||
rust_error_at(expr.get_locus (), "could not resolve identifier expression: %qs", expr.get_ident ().as_string ().c_str ()); | ||
return; | ||
} |
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.
that looks great - for style issues, could you also add braces to the above if
and else if
statements? this way the else
one isn't the only one with braces and it looks more uniform.
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.
yes, i'll get on it soon
I mistyped |
bfe2c62
to
3e993c9
Compare
gcc/rust/ChangeLog: * resolve/rust-late-name-resolver-2.0.cc (Late::visit): Add error emitting
gcc/rust/ChangeLog: * resolve/rust-late-name-resolver-2.0.cc (Late::visit): Add error emitting
3e993c9
to
cc3d16a
Compare
I fetched master from upstream and then rebase onto my branch so that the content matched this repository's master, not sure if there's any other way to have github not show false information that I actually modified 62 files??? |
it's showing me 1 file changed, so I think everything's good :) sometimes after a rebase the github frontend lags behind and takes a while to update. the commit list can also get messed up |
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.
thanks for taking care of this :) LGTM!
gcc/rust/ChangeLog:
From issue #2876 , I clone gcc locally, then run from build dir
to verify the crash.
Then i edit in-place of the recently cloned gcc the file
rust-late-name-resolver-2.0.cc
until the problem regarding the file goes away after rebuilding. The rest of the errors are in gcc error itselfI then transfer the newly edited portion to the gccrs codebase