`no_std` feature is backwards: a `use_std` feature should be used, which is part of the default features

[burtonageo]

Cargo features are supposed to be additive, which means the current no_std feature is backwards. This is an issue if you're writing a library, because there is currently no way to pass a negative switch (e.g. if I have a use_std flag, there is no way to say 'enable the no_std flag if it's not enabled.

The current system should be switched, so that there is a use_std feature, which is enabled in the default features.

[tormol]

Yeah. I learned this a few weeks ago.
When I added the feature I saw other crates do it that way, but thought no_std was easier to use.
I wish cargo had a more descriptive way of disabling features than default-features=false / --no-default-features.

[tbu-]

Fixed by 0cf9d8b.

[tomprogrammer]

I'll leave the issue open until I release the new version containing this commit today.

[emberian]

@tomprogrammer you still haven't released a new version. please make it 0.8 or something.

[tomprogrammer]

I've released version 0.8.0 with all pending changes listed in RELEASES.md.