The description does not specify any order for calling methods, and it's secret option C: the random tests will very probably generate tests where methods other than term will be called with arguments that have not been generated by term. Note that the reference solution solves this by explicitly calling term before accessing the other methods.
It would be possible to add a fixed test that addressed this hypothetical vulnerability, but it hardly seems worth it.
Fixed, issue was tests generating duplicate test titles which crashes scalatest.
Scalac already does that, @tailrec only causes compilation to fail if the compiler cannot rewrite it.
:)
I have a problem in python, how do I show you my proposal?
That solution doesn't pass in python, but I published an updated python version to invalidate other alternative solutions.
fixed
Interesting that the one you linked is 2 steps higher even though it is essentially the same thing. Is reverse egineering this one that hard...
I also get this bug, I hope it will be solve as soon as possible.
approved
Approved. Thank you!
( And thanks for fixng the Javascript description bug! )
The description does not specify any order for calling methods, and it's secret option C: the random tests will very probably generate tests where methods other than
termwill be called with arguments that have not been generated byterm. Note that the reference solution solves this by explicitly callingtermbefore accessing the other methods.It would be possible to add a fixed test that addressed this hypothetical vulnerability, but it hardly seems worth it.
Does this answer your question?
Thanks!
done
Loading more items...