To my mind the next steps are as follows:
- Continue discussion of flags and such on the intent to implement thread
(https://groups.google.com/forum/#!topic/v8-dev/Th-67YERn1I)
- Add a way to commit test262 tests to V8 that are not merged into the
official
test262 test suite yet. I envision e.g. a "test262-pending" directory or
similar.
- Add the running of a subset of test262 tests to the developer smoke test,
so
that we can have Array.prototype.contains tests committed to
test262-pending and
run by developers. Once the A.p.c tests are merged into test262 proper, we
will
still want to run them---but not the rest of the test262 suite---as part of
the
development process. Over time, as we add test262 tests instead of mjsunit
tests, we can expand the whitelisted set of tests to run.
Arv, Andreas and I can discuss the particulars of how to go about this in
person
at TC39 this week.
https://codereview.chromium.org/579973002/
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
