Since this (intent) is a big feature, I think it would be appropriate to run the entire suite in a module scope before it is shipped. Do you think it would take a lot of work to do that?
☆*PhistucK* On Wed, Jun 21, 2017 at 8:27 PM, Adam Klein <ad...@chromium.org> wrote: > On Wed, Jun 21, 2017 at 9:44 AM, PhistucK <phist...@gmail.com> wrote: > >> Has anyone run the full test262 test suite within a module scope, just to >> make sure all of the ordinary features work there the same? >> (I understand that from a point of view of an implementor, this might >> seem unnecessary, because it is the same engine, but who knows, it may >> uncover hidden peculiarities in the engine) >> > > I don't know if anyone has done such a thing, but test262 does already > include metadata that allows tests to be run in strict mode, sloppy > (non-strict) mode, or both; I could imagine it being extended to make it > easy for test runners to run tests as modules as well. > github.com/tc39/test262/issues would be the place to raise that feature > request. > -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.