Add missing const _IS_BIASED in test/mpsc.rs #149
Merged
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.
When I clone this repo to local and run
cargo test
, the compilation fails with "cannot find value_IS_BIASED
in this scope" after the expansion of macroselect
.flume/tests/mpsc.rs
Lines 174 to 187 in fcf3849
What's more, I forked this repo and tried github workflows, which failed due to same reason.
I find it uses a macro export from
crossbeam-channel
.flume
specifiescrossbeam-channel = "0.5.5"
in[dev-dependencies]
. However,crossbeam-channel
of version 0.5.5 has been yanked, so actually the newest version 0.5.13 is used. In the new version, a new value_IS_BIASED
is used in macrocrossbeam_channel_internal
, resulting in the error above.I find two use cases of
crossbeam_channel_internal
incrossbeam-channel
here:If this
select
macro is intended to work the same asselect
macro incrossbeam_channel_internal
, adding the const_IS_BIASED
with valuefalse
may help. After I added this value, thecargo test
succeeded.