On Sun, Aug 5, 2012 at 12:07 PM, Boris Zbarsky <[email protected]> wrote:
> If that ever happens the return value can be changed at that point. It's > silly to build in "extensibility" like this, imo, because there's > absolutely no reason for it: changing the return value to a superclass is > completely transparent to JS consumers. On the other hand, there's > certainly a drawback to having less-specific return values: it gives JITs > less information to work with in terms of optimizing the code. > I didn't say it was extensibility, just a leftover from something that was either considered and dropped or forgotten about. -- Glenn Maynard
