Skip to content

Commit a76bfdf

Browse files
committed
Update the user guide to mention findAndCheckEntryPoint for entry points without [shader(...)] attributes
1 parent 8cd77f1 commit a76bfdf

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

docs/user-guide/02-conventional-features.md

+1
Original file line numberDiff line numberDiff line change
@@ -655,6 +655,7 @@ In this example, the `vertexMain` shader indicates that it is meant for the `ver
655655
Rasterization, compute, and ray-tracing pipelines each define their own stages, and new versions of graphics APIs may introduce new stages.
656656

657657
For compatibility with legacy codebases, Slang supports code that leaves off `[shader(...)]` attributes; in these cases application developers must specify the names and stages for their entry points via explicit command-line or API options.
658+
Such entry points will not be found via `IModule::findEntryPointByName()`. Instead `IModule::findAndCheckEntryPoint()` must be used, and a stage must be specified.
658659
It is recommended that new codebases always use `[shader(...)]` attributes both to simplify their workflow, and to make code more explicit and "self-documenting."
659660

660661
> #### Note ####

0 commit comments

Comments
 (0)