This comment is hidden because it contains spoiler information about the solution
Is there any place you can reference that unrolls this lazyness for us? I find it hard to tell that it's using laziness.
Possibly you could also compare the regex's test method to an untouched regex's test method?
multipleof3Regex.test === /abc/.test
Was still able to cheat by overriding test method for a regex and then substituting its toString() function to get around that check. Tough one.
Loading collection data...
This comment is hidden because it contains spoiler information about the solution
Is there any place you can reference that unrolls this lazyness for us? I find it hard to tell that it's using laziness.
This comment is hidden because it contains spoiler information about the solution
This comment is hidden because it contains spoiler information about the solution
This comment is hidden because it contains spoiler information about the solution
Possibly you could also compare the regex's test method to an untouched regex's test method?
multipleof3Regex.test === /abc/.test
Was still able to cheat by overriding test method for a regex and then substituting its toString() function to get around that check. Tough one.