Closed this issue 2 years ago · 1 comments
Currently, a comment following a break; statement or something else can behave unexpectedly and cause the Interpreter to misbehave.
break;
644f687 fixed