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.

Sign up for GitHub

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

Jump to bottom

Clarify that free constants are always evaluated at compile time #1328

Merged
merged 2 commits into from
Mar 14, 2023
Merged

Clarify that free constants are always evaluated at compile time #1328

merged 2 commits into from
Mar 14, 2023

Commits on Feb 3, 2023

  1. Clarify that unnamed constants are always evaluated at compile time 

    See rust-lang/rust#93838
It seems like everyone is onboard with blessing this behavior as stable.
    @XrXr
    XrXr committed Feb 3, 2023
    Configuration menu
    Copy the full SHA
    86691a1 View commit details
    Browse the repository at this point in the history

Commits on Feb 14, 2023

  1. Adjust language to also cover named constants 

    Especially since it seems that there is no test in rust-lang/rust that
covers the unamed constant case (even though the implementation covers
it). rust-lang/rust#93838 (comment)
    @XrXr
    XrXr committed Feb 14, 2023
    Configuration menu
    Copy the full SHA
    021889f View commit details
    Browse the repository at this point in the history