You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wonder if we can catch cases like these where elision breaks things.
Basically, when the returned value has no relation to the inputs, lint that elision might not be wanted.
Exact heuristics would be tough to figure out, but I think it's doable (I've got a rough idea)
Ideally this should go into the compiler, but we can start it as a lint.
The text was updated successfully, but these errors were encountered:
Manishearth
added
E-hard
Call for participation: This a hard problem and requires more experience or effort to work on
S-needs-discussion
Status: Needs further discussion before merging or work can be started
and removed
E-hard
Call for participation: This a hard problem and requires more experience or effort to work on
labels
Aug 11, 2015
I wonder if we can catch cases like these where elision breaks things.
Basically, when the returned value has no relation to the inputs, lint that elision might not be wanted.
Exact heuristics would be tough to figure out, but I think it's doable (I've got a rough idea)
Ideally this should go into the compiler, but we can start it as a lint.
The text was updated successfully, but these errors were encountered: