On Fri, 12 Jun 2020 09:24:11 -0700 Georgy Yakovlev <gyakov...@gentoo.org> wrote:
> Not sure if --features=default will activate default set and how it > will react to being passed along. > > --no-default-features --features default > IDK, looks kinda unnatural. > > I have a feeling that we'll get more boilerplate if we pass > --no-default-features than if we don't. > > We can re-evaluate as time goes by, but for now I see no major benefit > and only downsides. One problem I stumbled onto is that while --no-default-features does work generically regardless of defined features, --features default does _NOT_ work generically, as it fails if there is no defined "default" feature. Another is some crates simply don't work with --no-default-features, and they need --features=std or similar in order to work. Hence, I don't think --no-default-features makes for a great default mechanism for rust. Its something you should only reach for when you know better.
pgpgZywecqaW5.pgp
Description: OpenPGP digital signature
