On Wed, 2014-09-17 at 17:28 -0700, Mike Shaver wrote: > My experience looking for similar things for Seneca would recommend: > > - relatively isolated subsystem: they should have to internalize less than > 1KLOC > - multiple meaningful milestones > - good existing test coverage > - few/no spec loose ends
Agreed. Humph eventually gave up on finding JS engine bugs for his students. Not enough isolated subsystems. Here are some decent first bugs in js/src: Bug 1069063 - Implement Array.prototype.contains https://bugzilla.mozilla.org/show_bug.cgi?id=1069063 Bug 911135 - ES6 Array.prototype.{map, filter, slice, splice} result is based on "constructor" property (basically, support subclassing Array) https://bugzilla.mozilla.org/show_bug.cgi?id=911135 Bug 1067049 - 'arguments' should be ES6 iterable https://bugzilla.mozilla.org/show_bug.cgi?id=1067049 I could scare up a few more fixing ES6 bugs, but they'd be boring. The main isolated subsystems in js/src are library facilities. -j _______________________________________________ dev-tech-js-engine-internals mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
