Make FutureResult non-Send when no-std
#335
Open
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.
Description
This PR updates the
FutureResulttype alias in the async persister implementation to support non-Sendfutures when thestdfeature is disabled.Previously, the
FutureResulttype always required theSendbound, which preventedno_stdenvironments from using non-Sendfutures. With this change, the bound is applied only when thestdfeature is enabled.This improves compatibility for embedded or
no_stdtargets while keeping fullSendsafety for standard environments.Notes to the reviewers
The change is minimal and fully backwards compatible.
It only affects compilation under
no_stdbuilds and does not modify any runtime behavior or APIs under thestdfeature.Please confirm that this approach aligns with the intended async API design and does not conflict with downstream usage expectations.
Changelog notice
Changed
FutureResulttype alias to allow non-Sendfutures inno_stdbuilds.