Closed davidben closed 10 years ago
Thanks, it appears to need a return Undefined()
at the end of that method in order to ensure that at least something is always returned. I wonder why other compilers haven't caught it (or maybe I just wasn't paying attention). But thanks, I will fix it at some point in the future.
Fixed by #35
Noticed this in the output of a package I was installing.
Unless that codepath never triggers, you probably want a
return Undefined();
or an exception at the end there, otherwise it might cause crashes.