3 ms·
>It is, for the example. It doesn't even look right for the example. This line: num += num2 + 3; Should be: num += _linqitems[i] + 3;
by nhebb 10y ago
>It is, for the example.
It doesn't even look right for the example. This line:
num += num2 + 3;
Should be:
num += _linqitems[i] + 3;
- OskarS 10y agoYeah, what the hell? That wont even compile. Is this thing even real? Why wouldn't the just use the actual output of their tool?
- matthewwarren 10y agoIt's just a typo on the README and it's been fixed now. The tool works fine, I've tried it out myself
- OskarS 10y agoOk, good. A thing like that doesn't inspire confidence, but presumably it was just a typo then.
- ygra 10y agoThey probably manually inlined a line like int num2 = _linqitems[i]; from the decompiled output. I'm fairly certain that if the transformation wouldn't result in compiling code, the compiler would refuse to compile it, resulting in no assembly to decompile. They also noted somewhere to have run the System.Linq tests and only one edge case involving Min/Max and NaN failed. Tests likely wouldn't run either if the code didn't compile.