[whatwg] new constructor method for Path2D

[Justin Novosad]

On Mon, Mar 10, 2014 at 2:14 PM, Rik Cabanier <cabanier at gmail.com> wrote:

> On Mon, Mar 10, 2014 at 11:07 AM, Joe Gregorio <jcgregorio at google.com
> >wrote:
>
> >
> > What part is slow, the decoding and re-encoding, or is just always the
> > encoding step
> > that is slow?
> >
>
> It's decoding/re-encoding of an already constructed path.


Can't the implementation just perform that work lazily the first time the
path is rasterized, and retain the cached result for subsequent use of the
path object?