XCode 9 Metal模板中VertexAttribute定义与属性映射疑问

Hey there! Let's unpack this confusion you're facing with the Xcode 9 Metal template—especially that Obj-C VertexAttribute enum and how it maps to Swift.

What does the VertexAttribute enum do? #

This Obj-C enum is a critical bridge between your CPU-side vertex data and GPU-side shader inputs. Metal requires explicit mapping of which vertex data properties (like position, texture coordinates) correspond to which input slots in your shader.

The enum values define the slot indices:

• VertexAttributePosition = 0 tells Metal that your vertex position data should be linked to the shader input marked with [[attribute(0)]]
• VertexAttributeTexcoord = 1 links your texture coordinate data to [[attribute(1)]] in the shader

Without this mapping, Metal wouldn't know how to feed your CPU data into the GPU's shader pipeline correctly.

Why does VertexAttributePosition become .position in Swift? #

This is thanks to Swift-Obj-C interoperability magic. When you import an Obj-C NS_ENUM into Swift, the compiler automatically cleans up the naming:

• The enum type name (VertexAttribute) becomes the Swift enum's name
• The enum case names lose the type prefix (VertexAttributePosition → .position, VertexAttributeTexcoord → .texcoord)

So in Swift, instead of writing the verbose Obj-C-style name, you can use the shorter, more idiomatic .position syntax. If you want to confirm the raw value matches, just check VertexAttribute.position.rawValue—it'll return 0, matching the Obj-C definition.

Why can't you jump to definitions or find documentation? #

A few reasons might be at play here:

• Xcode Indexing Glitches: Cross-language (Swift ↔ Obj-C) projects sometimes suffer from indexing bugs, especially in older Xcode versions like 9. Try cleaning your build folder (Shift + Cmd + K) and rebuilding the index (Cmd + Shift + P → "Rebuild Index") to fix jump-to-definition issues.
• Template-Specific Code: meshPositions and meshGenerics are custom variables/helpers defined in the template's Swift files (look for something like Mesh.swift or a dedicated vertex data file)—they aren't part of the Metal framework itself, which is why they don't have official documentation.
• Legacy Documentation Gaps: Early Metal documentation focused heavily on Obj-C, so Swift-specific interop details were sparse in older Xcode versions. Later versions of Xcode/Metal docs have better coverage, but the Xcode 9 template is a bit outdated.

Quick Tips to Debug #

• Double-check that ShaderTypes.h is included in your project's bridging header (or marked as part of the Objective-C bridging configuration) so Swift can see the enum.
• Print the raw values of the Swift enum cases to confirm they match the Obj-C definitions—this helps verify the mapping is working as expected.
• Look through all template files for where meshPositions is initialized; it's almost certainly an array of vertex structs that uses the VertexAttribute mapping to lay out data for Metal.

内容的提问来源于stack exchange，提问作者hyperknot