Re: [w3c/FileAPI] Correct handling of resizable ArrayBuffer? (Issue #219)

jasnell left a comment (w3c/FileAPI#219)

> If length having a side effect can cause issues for your implementation I think you've implemented it in the wrong way.

That's an obvious impl bug yes. That's not the question tho... the question is what is the correct behavior from a spec point of view. If `Since [AllowResizable] is not specified the correct behavior here is a TypeError` is the correct answer, that's what I need.

I don't have an opinion myself on whether they *should* be supported and I'm perfectly fine saying they are not; but I think @guybedford might have an opinion from a WASM perspective.

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

Message ID: <w3c/FileAPI/issues/219/4200649815@github.com>