Check that target supports atomic pointer operations before defining max size for Arc #168
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.
Resolving #167 cc: @jamesmunns
When building with, e.g.,
--target riscv32i-unknown-none-elf
and-F alloc
on the current main branch, the build will fail withdue to the lack of support on that target for atomic pointer operations (see: https://doc.rust-lang.org/alloc/sync/index.html).
Following the recommendation from the Rust docs, this gates definition of
POSTCARD_MAX_SIZE
foralloc::sync::Arc
behind a configuration check to confirm it is available on the target first.