chore: allow future_not_send lint at workspace level#267
Merged
branchseer merged 1 commit intomainfrom Mar 18, 2026
Merged
Conversation
The task scheduling workflow is a single-threaded async task, so Send bounds are unnecessary. Remove 22 per-item `#[expect]` annotations in favor of a single workspace-level allow in Cargo.toml. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Member
Author
Merge activity
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The task scheduling workflow is a single-threaded async task, so Send
bounds are unnecessary. Remove 22 per-item
#[expect]annotationsin favor of a single workspace-level allow in Cargo.toml.
Co-Authored-By: Claude Opus 4.6 (1M context) noreply@anthropic.com