Repository navigation
Use Array<T> | Iterable<T> ? #169
Description
Activity
Oh wait, that suggestion wouldn't actually solve it... I'd still have to cast it.
For some past discussion on this topic, see darionco/bikeshed-to-ts#6
I am still not sure what the right solution is. I was thinking for a long time of having both specialized (Array) and generic (Iterable) versions.
My general advice is to avoid naming these types in your code where possible. For example if you have a variable initialized as one big literal (most common), let type inference determine the type. For string enums, use e.g.
format: 'rgba8unorm' as constso it will infer a narrow type instead ofstring. For the WebGPU CTS this has solved most cases, so the number of cases where we have to go out of our way to get the correct typing is very small.Reacted by sdegutis
In the readme:
I think this is to allow you to pass arrays or iterables (such as returned from Array.entries() or Map.values() etc), right? But now I can't index it via
renderdesc.colorAttachments[0]because now it thinks it's not an array.Seems better to use something like
Iterable<T> | Array<T>or at least ArrayLike, so I can use this tutorial without issue.