| 07:52 | <annevk> | What hold Float16Array back from Stage 3? |
| 08:05 | <littledan> | What hold |
| 08:06 | <littledan> | If Safari wants Float16Array to happen, they can say so and explain why in committee next time, and I bet it would help (I imagine it will be brought back soon, especially if you prepare something like that) |
| 08:07 | <littledan> | More information on motivation and investigation into implementation difficulty |
| 08:07 | <littledan> | It wasn’t a “no” but a “maybe, we need to understand more” |
| 08:07 | <annevk> | Ah I thought we would have. And at least Chrome's canvas people also want it. |
| 08:12 | <littledan> | IIRC the canvas demand was mentioned; I suspect engine teams just want slightly more time to think about it |
| 08:22 | <annevk> | Fair I guess, for WebKit it wasn't estimated to be a big deal, but I heard other engine estimates that were way up and went up each time I heard it anew so I guess I rather not ask again 😊 |
| 08:23 | <littledan> | You all seem really efficient at doing certain things! |
| 15:14 | <bakkot> | I do hope to bring it back next meeting but yeah it'll depend on engines having had a chance to confirm it'll be feasible on all their supported targets |
| 15:15 | <bakkot> | I am almost certain it should be, from poking around, but they'll need to confirm for themselves |
| 15:15 | <bakkot> | Also I am reaching out to more of the web platform to see what integration work there is to be done in e.g. webgl and wasm |
| 15:26 | <annevk> | bakkot: cool, I noticed that Wasm doesn't have anything below i32, which was somewhat surprising |
| 15:26 | <annevk> | We'll also need a slight Web IDL update, but should be easy enough |