-
Notifications
You must be signed in to change notification settings - Fork 259
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
Add module organization suggestion doc #6509
Conversation
Suggest one method to keep slang modules organized in the file system. Closes shader-slang#4841
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
|
||
### Module Organization Suggestions | ||
|
||
- Top-level modules are those that are `import`ed by user code. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The terminology isn't very accurate: the util.slang
is the "main module file", and files being __included
are just files in that module. They are not "submodules".
Think about a module as a Visual Studio C++/C# Project, and a file is just a file in that project.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please let me know if I missed any inaccuracies.
cc0cdd9
to
99f8e40
Compare
Suggest one method to keep slang modules organized in the file system.
Closes #4841