Skip to content
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

Various improvements #63

Open
wants to merge 8 commits into
base: master
Choose a base branch
from
Open

Various improvements #63

wants to merge 8 commits into from

Conversation

Kixunil
Copy link
Owner

@Kixunil Kixunil commented Sep 6, 2024

See commits for details.

The man page generation was moved to the `cfg_me` tool and thus having
the feature enabled just wastes compile time and causes people problems
with `cargo_toml` yanking the crates frequently. Remove it from defaults
and document what it's for.
This can reduce the dependency tree if 1.0.0 is used elsewhere in the
crate and it looks better to depend on a stable version.
The library was created when `#[non_exhaustive]` didn't exist and
contained hacks to simulate it. This change removes the hacks in favor
of `non_exhaustive`.
`std` now has a dedicated type that makes the `void` crate obsolete.
Remove the dependency.
`Defaults` really represents user input and is not processed after input
validation, therefore the struct belongs to the `raw` module.
There were warnings emitted when the feature was off and it also
contained some deprecated stuff. Remove the deprecated functions and
feature gate the rest of the code to avoid warnings.
@Kixunil Kixunil added enhancement New feature or request refactoring Makes the code better, usually a groundwork for something else API breaking Will be semver-incompatible labels Sep 6, 2024
Previously there was a requirement to add
`#[macro_use] extern crate configure_me` in the crate which made usage
annoying but supported older versions of Rust which were unable to use
paths in macro invocations. Such old versions of Rust are no longer
supported therefore we can safely drop the requirement to have that
declaration.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API breaking Will be semver-incompatible enhancement New feature or request refactoring Makes the code better, usually a groundwork for something else
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant