-
Notifications
You must be signed in to change notification settings - Fork 156
Expand derived clusters #485
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
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @ryankurte (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
LGTM. |
I noticed that this causes invalid rust code to be generated for fields which only have a single |
I think it's better to split this PR. And place c9b18c7 in other one. |
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.
Nice!
Rebase to squash rustfmt and remove c9b18c7
This follows the same process as derived registers, and doesn't cover the case where the `derivedFrom` cluster is in a different scope.
5dd977e
to
c7d6061
Compare
bors r+ |
👎 Rejected by code reviews |
bors r=burrbull |
@smindinvern And of course I missed that this is missing a CHANGELOG entry. Would you mind PRing one? 😅 |
This PR addresses two issues encountered when attempting to process the svd file here.
EnumeratedValue
s that are "reserved", but aren't filtered out because they're named "other". They have an<isDefault>
child element, which is mutually exclusive with the<value>
child element according to the SVD schema, i.e. they don't represent a value that we would want to define in the generated code, and so can be skipped.When running
svd2rust-regress
locally 3 tests fail, but the same tests also fail onmaster
, so it seems there's no indication of a regression here.This seems to fix #462.