23w42a #1498
mat-1Annotations
11 warnings
|
use of `async fn` in public traits is discouraged as auto trait bounds cannot be specified:
azalea/src/container.rs#L25
warning: use of `async fn` in public traits is discouraged as auto trait bounds cannot be specified
--> azalea/src/container.rs:25:5
|
25 | async fn open_container(&mut self, pos: BlockPos) -> Option<ContainerHandle>;
| ^^^^^
|
= 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
|
25 - async fn open_container(&mut self, pos: BlockPos) -> Option<ContainerHandle>;
25 + fn open_container(&mut self, pos: BlockPos) -> impl std::future::Future<Output = Option<ContainerHandle>> + Send;
|
|
|
use of `async fn` in public traits is discouraged as auto trait bounds cannot be specified:
azalea/src/bot.rs#L85
warning: use of `async fn` in public traits is discouraged as auto trait bounds cannot be specified
--> azalea/src/bot.rs:85:5
|
85 | async fn mine(&mut self, position: BlockPos);
| ^^^^^
|
= 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
|
85 - async fn mine(&mut self, position: BlockPos);
85 + fn mine(&mut self, position: BlockPos) -> impl std::future::Future<Output = ()> + Send;
|
|
|
the feature `async_fn_in_trait` has been stable since 1.75.0-nightly and no longer requires an attribute to enable:
azalea/src/lib.rs#L4
warning: the feature `async_fn_in_trait` has been stable since 1.75.0-nightly and no longer requires an attribute to enable
--> azalea/src/lib.rs:4:12
|
4 | #![feature(async_fn_in_trait)]
| ^^^^^^^^^^^^^^^^^
|
= note: `#[warn(stable_features)]` on by default
|
|
use of `async fn` in public traits is discouraged as auto trait bounds cannot be specified:
azalea/src/container.rs#L25
warning: use of `async fn` in public traits is discouraged as auto trait bounds cannot be specified
--> azalea/src/container.rs:25:5
|
25 | async fn open_container(&mut self, pos: BlockPos) -> Option<ContainerHandle>;
| ^^^^^
|
= 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
|
25 - async fn open_container(&mut self, pos: BlockPos) -> Option<ContainerHandle>;
25 + fn open_container(&mut self, pos: BlockPos) -> impl std::future::Future<Output = Option<ContainerHandle>> + Send;
|
|
|
use of `async fn` in public traits is discouraged as auto trait bounds cannot be specified:
azalea/src/bot.rs#L85
warning: use of `async fn` in public traits is discouraged as auto trait bounds cannot be specified
--> azalea/src/bot.rs:85:5
|
85 | async fn mine(&mut self, position: BlockPos);
| ^^^^^
|
= 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
|
85 - async fn mine(&mut self, position: BlockPos);
85 + fn mine(&mut self, position: BlockPos) -> impl std::future::Future<Output = ()> + Send;
|
|
|
the feature `async_fn_in_trait` has been stable since 1.75.0-nightly and no longer requires an attribute to enable:
azalea/src/lib.rs#L4
warning: the feature `async_fn_in_trait` has been stable since 1.75.0-nightly and no longer requires an attribute to enable
--> azalea/src/lib.rs:4:12
|
4 | #![feature(async_fn_in_trait)]
| ^^^^^^^^^^^^^^^^^
|
= note: `#[warn(stable_features)]` on by default
|
|
clippy_check
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/toolchain@v1, actions-rs/clippy-check@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
clippy_check
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
clippy_check
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
clippy_check
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
clippy_check
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|