RoslynLinqRewrite – Compiles C# by rewriting and optimising LINQ expressions

Re:RoslynLinqRewrite – Compiles C# by rewriting and optimisi... by nhebb on Wednesday September 21, 2016 @02:43AM (#12545930)

>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;

[ Parent | on HN ]

Re:RoslynLinqRewrite – Compiles C# by rewriting and optimisi... by ygra on Wednesday September 21, 2016 @03:57AM (#12546219)

They 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.

[ Parent | on HN ]

Re:RoslynLinqRewrite – Compiles C# by rewriting and optimisi... by OskarS on Wednesday September 21, 2016 @03:12AM (#12546014)

Yeah, what the hell? That wont even compile. Is this thing even real? Why wouldn't the just use the actual output of their tool?

[ Parent | on HN ]

Re:RoslynLinqRewrite – Compiles C# by rewriting and optimisi... by matthewwarren on Wednesday September 21, 2016 @05:56AM (#12546733)

It's just a typo on the README and it's been fixed now.

The tool works fine, I've tried it out myself

[ Parent | on HN ]

Re:RoslynLinqRewrite – Compiles C# by rewriting and optimisi... by OskarS on Wednesday September 21, 2016 @09:02AM (#12547754)

Ok, good. A thing like that doesn't inspire confidence, but presumably it was just a typo then.

[ Parent | on HN ]