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

replace uses of ! with Void #80

Merged
merged 2 commits into from
May 11, 2018
Merged

replace uses of ! with Void #80

merged 2 commits into from
May 11, 2018

Conversation

japaric
Copy link
Member

@japaric japaric commented May 11, 2018

We are soon going to push for embedded library development on beta (1.27-beta) to minimize the
number of unstable features used in the ecosystem and ease the transition towards application
development on stable (1.28 or 1.29).

Unfortunately ! didn't make it into the beta release but we still need to make this crate work on
beta because a lot of crates depend on it. So this PR replaces the single use of the ! type (cf.
CountDown.wait) with the equivalent, but stable, Void type.

This is a [breaking-change]. Implementations of the CountDown trait will have to update the
signature of wait to return nb::Result<(), Void>.

cc @therealprof @hannobraun I'm going to publish v0.2.0 soon (ideally tonight). If there's
some breaking, but uncontroversial, change that should be included in it let me know ASAP so
we can land it before the release.

@japaric
Copy link
Member Author

japaric commented May 11, 2018

bors r+

bors bot added a commit that referenced this pull request May 11, 2018
80: replace uses of ! with Void r=japaric a=japaric

We are soon going to push for embedded *library* development on beta (1.27-beta) to minimize the
number of unstable features used in the ecosystem and ease the transition towards *application*
development on stable (1.28 or 1.29).

Unfortunately `!` didn't make it into the beta release but we still need to make this crate work on
beta because a lot of crates depend on it. So this PR replaces the single use of the `!` type (cf.
`CountDown.wait`) with the equivalent, but stable, `Void` type.

This is a [breaking-change]. Implementations of the `CountDown` trait will have to update the
signature of `wait` to return `nb::Result<(), Void>`.

cc @therealprof @hannobraun I'm going to publish v0.2.0 *soon* (ideally tonight). If there's
some **breaking**, but *uncontroversial*, change that should be included in it let me know ASAP so
we can land it before the release.

Co-authored-by: Jorge Aparicio <[email protected]>
@bors
Copy link
Contributor

bors bot commented May 11, 2018

Canceled

@japaric
Copy link
Member Author

japaric commented May 11, 2018

bors r+

bors bot added a commit that referenced this pull request May 11, 2018
80: replace uses of ! with Void r=japaric a=japaric

We are soon going to push for embedded *library* development on beta (1.27-beta) to minimize the
number of unstable features used in the ecosystem and ease the transition towards *application*
development on stable (1.28 or 1.29).

Unfortunately `!` didn't make it into the beta release but we still need to make this crate work on
beta because a lot of crates depend on it. So this PR replaces the single use of the `!` type (cf.
`CountDown.wait`) with the equivalent, but stable, `Void` type.

This is a [breaking-change]. Implementations of the `CountDown` trait will have to update the
signature of `wait` to return `nb::Result<(), Void>`.

cc @therealprof @hannobraun I'm going to publish v0.2.0 *soon* (ideally tonight). If there's
some **breaking**, but *uncontroversial*, change that should be included in it let me know ASAP so
we can land it before the release.

Co-authored-by: Jorge Aparicio <[email protected]>
@bors
Copy link
Contributor

bors bot commented May 11, 2018

Build succeeded

@bors bors bot merged commit ec1d608 into master May 11, 2018
@therealprof
Copy link
Contributor

@japaric Do they need to be breaking? I think there's a lot of stuff we should start getting in.

PR #56 looks like a go to me.
PR #72 looks good and is even breaking, however the two nits I raised were not addressed by @astro

@bergus
Copy link

bergus commented May 15, 2018

Meh, this sounds like a lot of unnecessary work for implementers of the hal. How long will it take until ! becomes stable, and all of this has to be changed back? (With another breaking change, unless you consider reem/rust-void#13)

peckpeck pushed a commit to peckpeck/embedded-hal that referenced this pull request Nov 10, 2022
81: Add features for spi and i2c r=eldruin a=zuckschwerdt

Adds the features `i2c` and `spi` for an optional dependency on `i2cdev` and `spidev`.

Discussion in rust-embedded#80.
Closes rust-embedded#80 

Co-authored-by: Christian W. Zuckschwerdt <[email protected]>
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.

3 participants