If you attempt to build a no-std target, and you forget to include #![no_std] (or you forget to remove a std feature in a dependency, or use a std-needing dependency), then it results in a fairly confusing error:
error[E0658]: use of unstable library feature 'restricted_std'
|
= help: add `#![feature(restricted_std)]` to the crate attributes to enable
I think that will be a frequent error that will be challenging for users to understand.
I don't know how to address that. It might be nice if cargo could know whether or not a target is intended to support "std", but that sounds challenging.
If you attempt to build a no-std target, and you forget to include
#, then it results in a fairly confusing error:I think that will be a frequent error that will be challenging for users to understand.
I don't know how to address that. It might be nice if cargo could know whether or not a target is intended to support "std", but that sounds challenging.