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

Eeprom Novella refactoring and move codes to extern repo #53

Open
pmnxis opened this issue Nov 14, 2023 · 1 comment
Open

Eeprom Novella refactoring and move codes to extern repo #53

pmnxis opened this issue Nov 14, 2023 · 1 comment

Comments

@pmnxis
Copy link
Owner

pmnxis commented Nov 14, 2023

Eeprom Novella refactoring and move codes to https://github.com/pmnxis/novella

@pmnxis
Copy link
Owner Author

pmnxis commented Nov 19, 2023

   Compiling billmock-app-rs v0.3.1 (/home/pmnxis/Develop/billmock-app-rs)
warning: [email protected]: This is not NDA serial device build.
warning: the feature `async_fn_in_trait` has been stable since 1.75.0-nightly and no longer requires an attribute to enable
  --> src/main.rs:10:12
   |
10 | #![feature(async_fn_in_trait)]
   |            ^^^^^^^^^^^^^^^^^
   |
   = note: `#[warn(stable_features)]` on by default

warning: method `test_mut_inh_then_ignore` is never used
   --> src/application/mutual_inhibit.rs:119:12
    |
99  | impl InputEvent {
    | --------------- method in this implementation
...
119 |     pub fn test_mut_inh_then_ignore(&self, mut_inh: &mut MutualInhibit) -> Self {
    |            ^^^^^^^^^^^^^^^^^^^^^^^^
    |
    = note: `#[warn(dead_code)]` on by default

warning: use of `async fn` in public traits is discouraged as auto trait bounds cannot be specified
   --> src/components/eeprom.rs:213:5
    |
213 |     async fn lock_read(
    |     ^^^^^
    |
    = note: you can suppress this lint if you plan to use the trait only in your own code, or do not care about auto traits like `Send` on the `Future`
    = note: `#[warn(async_fn_in_trait)]` on by default
help: you can alternatively desugar to a normal `fn` that returns `impl Future` and add any desired bounds such as `Send`, but these cannot be relaxed without a breaking API change
    |
213 ~     fn lock_read(
214 |         &self,
215 |         mutex: &Mutex<ThreadModeRawMutex, NovellaModuleControlBlock>,
216 ~     ) -> impl std::future::Future<Output = Self::InnerType> + Send;
    |

warning: use of `async fn` in public traits is discouraged as auto trait bounds cannot be specified
   --> src/components/eeprom.rs:218:5
    |
218 |     async fn lock_write(
    |     ^^^^^
    |
    = note: you can suppress this lint if you plan to use the trait only in your own code, or do not care about auto traits like `Send` on the `Future`
help: you can alternatively desugar to a normal `fn` that returns `impl Future` and add any desired bounds such as `Send`, but these cannot be relaxed without a breaking API change
    |
218 ~     fn lock_write(
219 |         &self,
220 |         mutex: &Mutex<ThreadModeRawMutex, NovellaModuleControlBlock>,
221 |         src: Self::InnerType,
222 ~     ) -> impl std::future::Future<Output = ()> + Send;
    |

warning: use of `async fn` in public traits is discouraged as auto trait bounds cannot be specified
   --> src/components/eeprom.rs:224:5
    |
224 |     async fn lock_write_zero(&self, mutex: &Mutex<ThreadModeRawMutex, NovellaModuleControlB...
    |     ^^^^^
    |
    = note: you can suppress this lint if you plan to use the trait only in your own code, or do not care about auto traits like `Send` on the `Future`
help: you can alternatively desugar to a normal `fn` that returns `impl Future` and add any desired bounds such as `Send`, but these cannot be relaxed without a breaking API change
    |
224 -     async fn lock_write_zero(&self, mutex: &Mutex<ThreadModeRawMutex, NovellaModuleControlBlock>);
224 +     fn lock_write_zero(&self, mutex: &Mutex<ThreadModeRawMutex, NovellaModuleControlBlock>) -> impl std::future::Future<Output = ()> + Send;

remove async later.

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

No branches or pull requests

1 participant