Join GitHub today
optimizer changes behavior when pattern matching Some(X) scrutinee when X's type assumed wrong #7540
The following program produces different results depending on whether it's compiled with
Console output unoptimized:
Console output under
One could argue whether:
In any case, it's a behavioral difference wrt the unoptimized run (and that must be the correct one).