Skip to content

allow dead_code and missing_docs in generated output #56

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

Closed
wants to merge 2 commits into from

Conversation

crawford
Copy link
Contributor

@crawford crawford commented Feb 6, 2017

Fixes #18

This adds #[allow(dead_code)] to all structures and methods to suppress
dead-code warnings when using the generated code.
This adds #[allow(missing_docs)] to the structs and methods as
neccessary, prefering to use the description from the SVD instead.
@japaric
Copy link
Member

japaric commented Feb 9, 2017

Thanks for the PR, @crawford.

If the generated code produces dead_code warnings, that indicates a bug in svd2rust or that svd2rust is being misused (e.g. you are not exposing the API as public).

And I'd rather fix the missing_docs warnings by actually documenting better the API rather than just sprinkling allow(missing_docs) here and there.

The docs generation will be revised in #53 so let's revisit this later.

@japaric japaric closed this Feb 9, 2017
@crawford
Copy link
Contributor Author

crawford commented Feb 9, 2017

Okay, I'll have to double check my setup to figure out why I get all of those warnings.

Looking forward to #53.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants