Myles C. Maxfield

Here is an example of the naming conflict, from a well-known library: https://github.com/WebKit/WebKit/blob/main/Source/WTF/wtf/Ref.h#L281

The check in https://github.com/xtermjs/xterm.js/blob/master/src/common/Platform.ts#L21: ``` export const isSafari = /^((?!chrome|android).)*safari/i.test(userAgent); ``` doesn't seem to catch [WKWebView](https://developer.apple.com/documentation/webkit/wkwebview?language=objc), which is the browser engine powering Safari. Safari's user agent string (on an iPad)...

I don't want to state any opinion (yet) about whether or not frames (`getCurrentTexture()`) should march onward for canvases that are potentially unobserved in various ways (e.g. not hooked up...

Also, why would we ever swap more frequently than HTML5's Update the Rendering step? That seems wasteful.

> When would the caller of a .then() or await reliably know that the Promise is already resolved and not pending? As I mentioned in the meeting, there are 2...

This issue is a dup of https://github.com/gpuweb/gpuweb/issues/1842 which has a resolution (but isn't closed yet because there's a pending TODO)

(Note: this is *NOT* a dup of https://github.com/gpuweb/gpuweb/issues/889, which is about overlapping binding _numbers_ in the shader source, not about overlapping _regions_ of buffers)

> [SHORTNAME] assumes no aliasing is present in the program. This seems a little draconian ... You can't make 2 pointers to the same variable? Even with the logical-mode restrictions,...

> Much of the discussion in this bug seems to be about implementing inout using pointers. Is that the concern for WGSL? I thought it was implementing pointers using inout....

Last week, I was trying to draw a distinction between this (please forgive the not-perfect WGSL): ``` fn foo() { var x = 4; let y = &x; let z...