Skip to content

enable #[no_std] use by providing std feature#562

Merged
mrmonday merged 1 commit intolibpnet:masterfrom
Felix-El:no_std
May 12, 2022
Merged

enable #[no_std] use by providing std feature#562
mrmonday merged 1 commit intolibpnet:masterfrom
Felix-El:no_std

Conversation

@Felix-El
Copy link
Copy Markdown
Contributor

Also adds a dependency on no_std_net for no_std addresses.

#133

Adds a dependency on no_std_net for no_std addresses
@mrmonday
Copy link
Copy Markdown
Contributor

This looks great - thanks!

It would be good to have nostd tested in CI so this doesn't regress, but that can be done in another PR later on.

@mrmonday mrmonday merged commit 9e06711 into libpnet:master May 12, 2022
@fujiapple852
Copy link
Copy Markdown

fujiapple852 commented May 24, 2022

@mrmonday @Felix-El this change has bumped the effective MSRV to 1.60 due to the use of the new dep-name?/feature-name Cargo syntax, specifically this change.

Was this intended?

@Felix-El
Copy link
Copy Markdown
Contributor Author

I'm open to using a pre-1.60 Cargo syntax. I'm just not aware of it. Is there an alternative syntax for requesting a feature conditionally without forcing the dependency in?

@fujiapple852
Copy link
Copy Markdown

fujiapple852 commented May 24, 2022

@Felix-El I'm not completely sure, the original GH RFC suggests "There exists a kind of workaround" which doesn't inspire confidence!

No issue with bumping the MSRV from time to time, it may be useful to add the conventional rust-version attribute to Cargo.toml and mention bumps prominently in release notes and the README to save people having to figure it out.

@mrmonday
Copy link
Copy Markdown
Contributor

We used to support older Rust versions - we changed at some point to only support the latest stable Rust.

This said, I'm happy to accept a PR to make these changes place nicely with older Rust versions if that's possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants