Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix broken link in 09-reflection.md #5655

Merged
merged 3 commits into from
Nov 25, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/user-guide/08-compiling.md
Original file line number Diff line number Diff line change
Expand Up @@ -829,7 +829,7 @@ The details of how Slang computes layout, what guarantees it makes, and how to i
Because the layout computed for shader parameters may depend on the compilation target, the `getLayout()` method actually takes a `targetIndex` parameter that is the zero-based index of the target for which layout information is being queried.
This parameter defaults to zero as a convenience for the common case where applications use only a single compilation target at runtime.

See [Using the Reflection API] chapter for more details on the reflection API.
See [Using the Reflection API](reflection) chapter for more details on the reflection API.

### Linking

Expand Down
4 changes: 2 additions & 2 deletions docs/user-guide/09-reflection.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ The Slang API allows layout to be queried on any program object represented by a
slang::ProgramLayout* layout = program->getLayout();
```

Please see the [Compiling Code with Slang](/user-guide/compiling) section on creating program objects.
Please see the [Compiling Code with Slang](compiling) section on creating program objects.

Note that just as with output code, the reflection object (and all other objects queried from it) is guaranteed to live as long as the request is alive, but no longer.
Unlike the other data, there is no easy way to save the reflection data for later user (we do not currently implement serialization for reflection data).
Expand Down Expand Up @@ -224,4 +224,4 @@ unsigned int attribCount = funcReflection->getUserAttributeCount();
slang::UserAttribute* attrib = funcReflection->getUserAttributeByIndex(0);
const char* attribName = attrib->getName();

```
```