Garrett Johnson

> Does the dev/user needs to be aware of this or can we just take care of it for them? I don't know. I don't think we can but perhaps...

@mrdoob I see it hasn't been added to any milestone -- is this blocked because it can't be implicitly enabled? This PR just enhances the existing Material.alphaToCoverage flag and doesn't...

Is this previous issue related? https://github.com/mrdoob/three.js/issues/17384 It looks like this PR is changing the behavior of log depth buffer to only apply to vertices rather than fragments which I don't...

The `copy` and `clone` functions should be aware of it, as well, and it should be available on `InstancedBufferAttribute`. I think I would expect this to be on `BufferAttribute` at...

> Hmm... Should these classes be used for float attributes? There is value I think to using 8 or 16 byte integer buffers for float values in terms of memory...

> How about creating Float8BufferAttribute and Float16BufferAttribute for these cases? In practice I've never used any of the typed BufferAttribute classes -- I've just never seen the purpose because I...

> I guess I'm missing something here and in https://github.com/mrdoob/three.js/issues/21595 though, why is it we cannot intepret the data this way? > > array type | normalized | glsl type...

> Casting from int to float before use does not seem impossible or inherently worse than the alternative, It's definitely not impossible but I think it is inherently worse. There...

I can see that - `.integer` could be replaced with something that declares the feature differently and maybe more clearly: ```js attribute.shaderFormat = THREE.IntType; attribute.integerUpload = true; ``` But for...

I like this change 👍 The name might be a big vague, though. When I saw the title of the PR I though this was going to be a function...