Ben Smith

> since ArrayBuffers are mutable by JS once returned, I think it's almost always necessary to return a copy Right, unless the ArrayBuffer was detached, to represent transfer. But no...

> Right, that's what I said in my initial comment on slice Sorry, misread that comment. > We're talking about adding overloads to some existing methods, in a way that...

Here's an example of what I was thinking. Imagine you are using a zlib wasm module library. You don't know what the user of the library is going to do...

@RReverser I agree that it would be nice to make the out-of-date design documents less prominent. But when this has come up in the past, we've always decided to keep...

@RReverser Looks like you were a "maintainer" before, I switched you to an "admin" of https://github.com/webassembly/website. :-)

Oh, of course. Whoops! Here's what I see for "Popular Content", on the traffic page: Content | Views | Unique visitors -- | -- | -- WebAssembly/design: WebAssembly Design Documents...

@RReverser AFAIK, none of the documents are relevant anymore, aside from as a historical artifact. But I'm not sure we've agreed that they should be moved to a subdirectory. Is...

I see what you mean. Personally I don't think any docs here should be surfaced on webassembly.org, so it's probably better to remove. Maybe others disagree, though.

@RReverser Those ones all seem pretty good to me. I don't know that there are better resources, so I think it's OK to keep those.

@sammax Ah, good point that this integrates nicely with #1348. You may want to incorporate into the design above. So you can reference an address directly in the data section...