Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Compiler Error is Caused With `^` in Code

See original GitHub issue

Describe the bug When I run Stryker on my code (which can be found here), it tries to replace ^ with ==, and in this case, that’s incorrect.

Expected behavior Stryker runs without generating a compiler error.

Desktop (please complete the following information):

OS: Windows
Type of project: .NET 5.0
Stryker Version: 0.22.4

Issue Analytics

State:
Created 2 years ago
Comments:8 (5 by maintainers)

Top GitHub Comments

1reaction

rouke-broersmacommented, Jun 23, 2021

That would be a good improvement! And you’re correct, we should be doing more perf work…

0reactions

JasonBockcommented, Jun 22, 2021

I wouldn’t argue that bet. But with anything perf-related, it’s always good to get the numbers.

But here’s another thought. In the case that I presented, the code is doing ^ on two NumericLiteralExpressionSyntax nodes. Would it be possible to do a look at the nodes being used for ExclusiveOrExpressionSyntax, and for the simple cases you can run into (e.g. it’s using NumericLiteralExpressionSyntax or FalseLiteralExpressionSyntax), you can determine which mutator to use. For other cases where something like an InvocationExpressionSyntax or IdentifierNameSyntax is in play, you can’t, so you’ll still have to do both mutations for ^.