Re: [css-houdini-drafts] [worklets] Speculative evaluation

The CSS Working Group just discussed `Custom Paint`.

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> Topic: Custom Paint<br>
&lt;dbaron> Github: https://github.com/w3c/css-houdini-drafts/issues/406<br>
&lt;fantasai> ??: Ideally we'd have future-proofing simialr to tearing down of worklets now and again for this as well, but to really do that would require existing impls to do speculative execution for no good reason at all<br>
&lt;fantasai> ??: That's a hard sell, so that's not what we're asking for<br>
&lt;jack> fantasai: that's till<br>
&lt;fantasai> ??: What we are asking for is to explicitly allow speculative execution in the spec<br>
&lt;fantasai> s/??/jack/<br>
&lt;jack> ??? = till<br>
&lt;dbaron> s/??/till/<br>
&lt;fantasai> iank_: Basically what we're asking for is a section like " ... user agents my speculatively invoke this function, giving what it thinks it an object size and size could be at a future point in time"<br>
&lt;fantasai> till: We'll work on a PR<br>
&lt;fantasai> iank_: I think this belongs in the paint spec, not the worklets spec though<br>
&lt;fantasai> till: Ideally we should have ability to do this in as many worklets as possible, but doesn't make sense in other places<br>
&lt;fantasai> iank_: Maybe say in worklets spec that downstream specs may choose to do this<br>
&lt;fantasai> dino: What would be an extra parameter?<br>
&lt;fantasai> dino: What's the API for this?<br>
&lt;fantasai> dino: There's a paint function that gets size and style map<br>
&lt;fantasai> iank_: NO additional API<br>
&lt;fantasai> dino: Just the style map would have speculative?<br>
&lt;fantasai> iank_: Yes<br>
&lt;fantasai> till: Should already bee somwhat future-proofed because of req in spec intended to prevent you from relying on state, should hopefully make this possile<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/406#issuecomment-319323642 using your GitHub account

Received on Tuesday, 1 August 2017 09:48:23 UTC