[RFC] Normalizing our type naming conventions #1593
aleksanderkatan
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I see some potentially unintuitive names among our types. I think that we should consider coming up with more general rules on how we name the types of our resources.
The points of discussion:
d.vec2f,d.v2fandd.Vec2.I currently see no ideal way of addressing this. Renaming
v2ftovec2fwould cause even more confusion. I think that we shouldn't use lowercase names for types. Renaming toVec2fSchemaandVec2fInstanceseems too explicit and long.TgpuvsWgslvs <nothing>.We have
TgpuBuffer,TgpuBindGropuLayout,TgpuFn,TgpuVar,WgslStruct,WgslArray,Ptr,Atomic,Vec2f. I think that we should get rid of theWgslprefix, but I am not sure where to put the line on what uses theTgpuprefix.AnyWgslData,AnyLooseData,AnyDataandBaseData.I think that it may be argued that
d.v2fis more of aDatathand.Vec2f. We could renameDatatoSchema, but I'm not sure if we could considerPtr,Atomicor vertex formats to be data schemas.Suggestions welcome.
Beta Was this translation helpful? Give feedback.
All reactions