-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
[Rust] #7659 broke union-typed fields with number in name #7782
Comments
@CasperN, could you take a look? |
Hi @dbaileychess! You reviewed the change. Could you take a look? Maybe this is an easy fix? This is a regression in the code generator for rust. |
Ping @CasperN @dbaileychess. |
#7111 Related |
@dbaileychess Since this has been fixed now and v23.5.26 is out, could you also publish that release to crates.io? |
@CasperN you do this right? |
Done |
This issue is stale because it has been open 6 months with no activity. Please comment or label |
This issue was automatically closed due to no activity for 6 months plus the 14 day notice period. |
… (google#7964) Co-authored-by: Derek Bailey <derekbailey@google.com>
… (google#7964) Co-authored-by: Derek Bailey <derekbailey@google.com>
The new flatc 23.1.4 generates broken Rust code when a field with a union type contains a number.
This produces references to
field_42_type()
in the generated code, but the method is correctly calledfield42_type()
.I pinpointed this to commit a078130 from #7659. flatc built from parent commit produces correct code.
The text was updated successfully, but these errors were encountered: