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.

Sign up for GitHub

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

Jump to bottom

GPIO: C-FAILURE violation #2665

Open
playfulFence opened this issue Dec 2, 2024 · 0 comments
Open

GPIO: C-FAILURE violation #2665

playfulFence opened this issue Dec 2, 2024 · 0 comments
Labels
1.0-blocker peripheral:gpio GPIO peripheral

Comments

@playfulFence
Copy link
Contributor

From Rust APU Guidelines:
C-FAILURE: Function docs include error, panic, and safety considerations.

We're somewhat good in terms of # Safetys, but not # Errors and # Panics
@playfulFence playfulFence added peripheral:gpio GPIO peripheral status:needs-attention This should be prioritized 1.0-blocker labels Dec 2, 2024
@github-project-automation github-project-automation bot moved this to Todo in esp-rs Dec 2, 2024
@playfulFence playfulFence removed the status:needs-attention This should be prioritized label Dec 2, 2024
@playfulFence playfulFence changed the title GPIO: C-FALIURE violation GPIO: C-FAILURE violation Dec 2, 2024
@playfulFence playfulFence changed the title GPIO: C-FAILURE violation GPIO: C-FAILURE violation Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
1.0-blocker peripheral:gpio GPIO peripheral
Projects
esp-rs
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
1 participant
@playfulFence