On 2015/02/19 16:32:59, rossberg wrote:
On 2015/02/19 16:26:17, arv wrote:
> On 2015/02/19 16:19:41, rossberg wrote:
> > On 2015/02/19 16:15:42, marja wrote:
> > > On 2015/02/19 13:23:05, rossberg wrote:
> > > > Good question. Most existing tests will probably not work,
for 'var'
> alone.
> > > > Maybe it's good enough to have a number of dedicated strong mode
test
> > > programs.
> > > > If something really gets ruled out accidentally then I suppose we
gonna
> find
> > > out
> > > > relatively quickly...
> > >
> > > ... how would we find it out though if we only run our small and few
> dedicated
> > > test progs w/ strong mode, and no other code?
> >
> > Yeah, I think once we have a critical mass of features, we should port
some
> > interesting programs to strong mode as tests. We could also try to run
(the
> > strongified version of) Traceur as a test. Arv, is Traceur pure ES6?
>
> Yes. Right now we compile it to ES5 but there is an option to compile
it to
ES6.
> We have granular flags for everything and I was planning to start using
io.js
> and keep things io.js supports (let, generators, for-of etc).
Okay, what does "compile to ES6" mean in this case? If the Traceur
sources are
pure ES6, could an ES6-ready VM perhaps even run Traceur itself without
bootstrapping through self compilation first?
Yes. If an engine supports all of ES6 no compilation is needed. (I know we
have
cases where derived classes do not call super() for performance reasons.)
https://codereview.chromium.org/939063002/
--
--
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.
