Skip to content

Remove the requirement for multicore tasks to never return #594

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

Merged

Conversation

ithinuel
Copy link
Member

@ithinuel ithinuel commented May 4, 2023

Alternative solution to #592

@ithinuel ithinuel force-pushed the do-not-require-multicore-callback-to-never-return branch from bb47c10 to b277b1e Compare May 4, 2023 07:09
@jannic
Copy link
Member

jannic commented May 4, 2023

This is a breaking change, as proven by the failing doc test, https://github.com/rp-rs/rp-hal/actions/runs/4880039111/jobs/8707219403?pr=594

In the end, it's a tradeoff.

Pro:

  • simplifies the code
  • voids exposing the Never type (assuming it's still unstable for good reasons)

Cons:

  • breaking change
  • the Never type better describes the intention

Any arguments I missed?

@ithinuel ithinuel force-pushed the do-not-require-multicore-callback-to-never-return branch from 0ff44c4 to a3a18bb Compare May 4, 2023 22:20
@ithinuel ithinuel added this to the 0.9.0 milestone May 13, 2023
@jannic jannic added the breaking change This pull request contains a SemVer breaking change label May 14, 2023
@jannic jannic merged commit 4ab43cb into rp-rs:main May 20, 2023
@ithinuel ithinuel deleted the do-not-require-multicore-callback-to-never-return branch May 20, 2023 21:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking change This pull request contains a SemVer breaking change
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants