-
Notifications
You must be signed in to change notification settings - Fork 224
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
Naming lock types #611
Comments
Does passing it using the |
Unfortunately no, because it's a trait object function. |
@LU15W1R7H Could you provide some MWE showcasing the issue you have? |
Is it when you want to embed the function into a trait that the problem occurs. I mean in general you can pass a https://github.com/rtic-rs/cortex-m-rtic/blob/master/examples/generics.rs |
Yes, it's about trait object safety!
That's what i used in the problem branch, which doesn't compile. |
I want to pass a shared resource to a function, but I'm unable to name the lock.
The path
app::shared_resources::resource_that_needs_to_be_locked
is not accessible, asapp::shared_resources
is private.Also the generated name
resource_that_needs_to_be_locked
is inconvenient.The text was updated successfully, but these errors were encountered: