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

Discarding evaluatable bounds and soundness #40

Open
lcnr opened this issue Mar 23, 2022 · 0 comments
Open

Discarding evaluatable bounds and soundness #40

lcnr opened this issue Mar 23, 2022 · 0 comments
Labels
A-eval-bounds Const evaluatability bounds C-design-docs Category: This is part of our design documentation K-behavior Document Kind: regarding user visible behavior P-optional Priority: not strictly required S-active

Comments

@lcnr
Copy link
Contributor

lcnr commented Mar 23, 2022

What is this

This is a design document for const generics. Any discussions about its content should be on zulip. The conclusions of these discussions should then be edited back into this issue. Please do not post any comments directly in this issue.

Content

Assuming that we add const evaluatability bounds, there might be a lot of cases where explicit bounds are obviously correct but cannot be discarded automatically be the compiler.

fn small<const N: usize>()
where
    evaluatable { N - 2 },
{}

fn big<const N: usize>()
where
    evaluatable { N / 4 - 2 }

fn uses_both<const N: usize>()
where
    ...
{
    small();
    big();
}

To satisfy the bounds of small and big we would have to add both bounds to uses_both, even though the bound of big also guarantees that the bound of small holds. This is impossible to verify for the compiler in the general case.

It would therefore be nice to somehow discard the bound of small as the author of uses_both without being able to prove that it must hold.

How to do that is still unclear however.

@lcnr lcnr added C-design-docs Category: This is part of our design documentation K-behavior Document Kind: regarding user visible behavior P-optional Priority: not strictly required S-active A-eval-bounds Const evaluatability bounds labels Mar 23, 2022
@rust-lang rust-lang locked and limited conversation to collaborators Mar 23, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A-eval-bounds Const evaluatability bounds C-design-docs Category: This is part of our design documentation K-behavior Document Kind: regarding user visible behavior P-optional Priority: not strictly required S-active
Projects
None yet
Development

No branches or pull requests

1 participant