Skip to content
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

Legalize C-QUESTION-MARK violation #2929

Merged
merged 2 commits into from
Jan 10, 2025

Conversation

playfulFence
Copy link
Contributor

@playfulFence playfulFence added the skip-changelog No changelog modification needed label Jan 10, 2025
@@ -13,6 +13,7 @@ In general, the [Rust API Guidelines](https://rust-lang.github.io/api-guidelines
## Amendments to the Rust API Guidelines

- `C-RW-VALUE` and `C-SERDE` do not apply.
- `C-QUESTION-MARK`: `?` is not applicable in the context of the `main` function in our driver, documentation example makes no sense.
Copy link
Contributor

@bugadani bugadani Jan 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- `C-QUESTION-MARK`: `?` is not applicable in the context of the `main` function in our driver, documentation example makes no sense.
- `C-QUESTION-MARK`: `?` is not applicable in the context of the `main` function in our driver.

Doc examples do make sense, just not with the question mark 🙃

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤣

@playfulFence playfulFence requested a review from bugadani January 10, 2025 13:32
@jessebraham jessebraham enabled auto-merge January 10, 2025 13:33
@jessebraham jessebraham added this pull request to the merge queue Jan 10, 2025
Merged via the queue into esp-rs:main with commit e62141f Jan 10, 2025
28 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
skip-changelog No changelog modification needed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants