We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
const_fn attribute currently only accepts string literals as version requirements, like the current cfg_version does.
const_fn
cfg_version
#[const_fn("1.36")] const fn func() { /* ... */ }
Should we accept numeric literals directly, like the original RFC or rustversion crate?
#[const_fn(1.36)] const fn func() { /* ... */ }
The text was updated successfully, but these errors were encountered:
Stabilization report of cfg_version (rust-lang/rust#64796 (comment)) says:
Literal-free invocations like version(1.50) do cause errors just as version(foo) does.
version(1.50)
version(foo)
Closing -- I prefer to keep the same api as cfg_version.
Sorry, something went wrong.
No branches or pull requests
const_fn
attribute currently only accepts string literals as version requirements, like the currentcfg_version
does.Should we accept numeric literals directly, like the original RFC or rustversion crate?
The text was updated successfully, but these errors were encountered: