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

Bump dependency on vcell to version 0.1.3 #83

Merged
merged 1 commit into from
Aug 2, 2023

Conversation

jannic
Copy link
Member

@jannic jannic commented Aug 2, 2023

The depenency used to be on version 0.1.0, but the pac doesn't actually compile with that version:

error[E0599]: no method named `as_ptr` found for struct `vcell::VolatileCell` in the current scope
   --> src/generic.rs:101:23
    |
101 |         self.register.as_ptr()
    |                       ^^^^^^ method not found in `VolatileCell<<REG as RegisterSpec>::Ux>`

as_ptr was added in version 0.1.1 of vcell, but that version is marked as yanked for unknown reasons. (japaric/vcell#13)

Version 0.1.2 would have been another option, but 0.1.3 contains a fix for japaric/vcell#5 which looks important.

The depenency used to be on version 0.1.0, but the pac doesn't actually
compile with that version:

```
error[E0599]: no method named `as_ptr` found for struct `vcell::VolatileCell` in the current scope
   --> src/generic.rs:101:23
    |
101 |         self.register.as_ptr()
    |                       ^^^^^^ method not found in `VolatileCell<<REG as RegisterSpec>::Ux>`
```

`as_ptr` was added in version 0.1.1 of vcell, but that version is marked
as yanked for unknown reasons. (japaric/vcell#13)

Version 0.1.2 would have been another option, but 0.1.3 contains a fix for
japaric/vcell#5 which looks important.
@jannic jannic merged commit 9e77694 into rp-rs:main Aug 2, 2023
4 checks passed
@jannic jannic deleted the fix-vcell-dependency branch August 2, 2023 09:25
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.

2 participants