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.
Omitting condition section in standard for-loop breaks stryker
See original GitHub issueWhen you have a code like this:
for(let i=0;;i++) {
actual behaviour stryker will fail with: [2016-10-21 17:53:14.612] [ERROR] stryker-cli - an error occurred Error: The mutator named ‘RemoveConditionals’ caused an error: TypeError: Cannot read property ‘nodeID’ of null
expected behaviour What is expected: stryker does not supposed to fail in this case. While it’s not idiomatic (and most probably could be rewritten in a more readable fashion) this is 100% valid code.
if there will be any valid expression condition expression in for loop, this will work, so it’s enought to have:
for(let i=0;true;i++) {
how to reproduce I’ve created a minimal example.
git clone https://github.com/RachelSatoyama/bugreport.gitcd bugreport/stryker-for-loop && npm installnpm run stryker
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Yeah i agree with @RachelSatoyama . Could we mutate it to be
for(;false;)?It is. Thanks!