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

metabug: const_eval bugs from type confusion and/or overflow #23897

Closed
pnkfelix opened this issue Mar 31, 2015 · 5 comments
Closed

metabug: const_eval bugs from type confusion and/or overflow #23897

pnkfelix opened this issue Mar 31, 2015 · 5 comments
Assignees
Labels
A-type-system Area: Type system C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC metabug Issues about issues themselves ("bugs about bugs")

Comments

@pnkfelix
Copy link
Member

metabug: const_eval bugs from type confusion and/or overflow

(I am collapsing these seemingly distinct categories into one, because I have observed cases where a seeming failure to catch an overflow, or signaling an overflow where none should exist, can sometimes be traced to the const-evaluator being confused about the type of the expression in question.)

@pnkfelix
Copy link
Member Author

(tagging as A-typesystem since that's what @steveklabnik seems to often do, though I am currently wondering if we should actually have an A-consteval label at this point...)

@steveklabnik
Copy link
Member

Yeah, with this many issues...

@steveklabnik
Copy link
Member

Triage: this is a metabug, some stuff has changed, but not all of it.

@Mark-Simulacrum Mark-Simulacrum added the C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC label Jul 22, 2017
@pnkfelix
Copy link
Member Author

pnkfelix commented Jan 8, 2018

Hmm are we close to being able to close this metabug? I see almost all of the linked issues are now closed; the one remaining one is rust-lang/rfcs#1071, which is more ... philosophical...?

@pnkfelix
Copy link
Member Author

pnkfelix commented Jan 8, 2018

Yes at this point I think #30587 resolved all of our known issues here.

@pnkfelix pnkfelix closed this as completed Jan 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-type-system Area: Type system C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC metabug Issues about issues themselves ("bugs about bugs")
Projects
None yet
Development

No branches or pull requests

3 participants