Re: [w3c/ServiceWorker] Tee-ing Cache.put()? (#1367)

How is this kind of teeing more constrained than `clone()`? Naïvely, I'd think this could also be optimized by storing the knowledge that there's a clone floating around and not actually do much cloning until it starts mattering somehow.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/1367#issuecomment-445455844