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

Investigate C-INTERMEDIATE for all stabilized drivers #2820

Open
bugadani opened this issue Dec 16, 2024 · 1 comment
Open

Investigate C-INTERMEDIATE for all stabilized drivers #2820

bugadani opened this issue Dec 16, 2024 · 1 comment
Labels
1.0-blocker investigation Not needed for 1.0, but don't know if we can support without breaking the driver.

Comments

@bugadani
Copy link
Contributor

cc #2784

@bjoernQ
Copy link
Contributor

bjoernQ commented Dec 19, 2024

To avoid breaking changes in future:

To resolve this I guess for the non-error case we need to carefully look at every function returning ! or Result<(),E> (or where Result::T is a simple type)

For the error case we could consider that every error variant contains a payload, e.g. MaxDmaTransferSizeExceeded(MaxDmaTransferSizeExceededInfo), - initially that's just an empty struct (non-exhaustive) - if we ever consider to provide more information we could extend that struct without a breaking change

However, I'm not sure that is worth it

@MabezDev MabezDev removed the status:needs-attention This should be prioritized label Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.0-blocker investigation Not needed for 1.0, but don't know if we can support without breaking the driver.
Projects
Status: Todo
Development

No branches or pull requests

3 participants