-
-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does not work in no-std environment #262
Comments
The second place where Line 49 in 1809d7c
You can see that snafu's NOTE: |
Thank you for your issue! This is definitely not intentional, we should disable std in my fork and put backtraces behind a feature that is disabled by default. |
Also JER should be put behind a feature, as |
@koxu1996 Can you check now, as we now should compile with the latest nom-bitvec |
I am unable to compile my project due to
found duplicate lang item panic_impl
, which appears to be caused bystd
library being indirectly included byrasn
😨. Even though this library is claimed asno_std
its dependencies are not!Where
std
gets included?Latest rasn v0.8.2 depends on custom nom parser with bitvec:
This need to be discussed. Why is it custom? Probably because upstream is not supporting
bitvec v1
- see rust-bakery/nom-bitvec#1, and relevant PR got stuck. It seems that @XAMPPRocky released fork as renamed package with tag 0.2.0. The different between fork source code and files published in crates.io made my investigation more difficult.Okay, so let's use crates.io as the source of truth. You can see that
bitvec-nom2
depends onbitvec v1
:Default features are not disabled, so
std
gets included:NOTE: I was able to track it down with
cargo tree -e features
.The text was updated successfully, but these errors were encountered: