diff options
| author | Elie Michel <eliemichel@users.noreply.github.com> | 2024-05-30 20:59:39 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-05-30 11:59:39 -0700 |
| commit | 523a637a7a44858140d6b22746daf9cf5281772e (patch) | |
| tree | f1c7c254a754fe3037f3c963effcce5cc2b32477 | |
| parent | daec0a3d00576f0d76ba2d257380a15f9e2a437f (diff) | |
Fix confusion in Translation Units doc (#4245)
I think the sentence was saying the opposite of what it meant!
Co-authored-by: Yong He <yonghe@outlook.com>
| -rw-r--r-- | docs/user-guide/08-compiling.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/user-guide/08-compiling.md b/docs/user-guide/08-compiling.md index 69ead7b81..5701354a6 100644 --- a/docs/user-guide/08-compiling.md +++ b/docs/user-guide/08-compiling.md @@ -31,7 +31,7 @@ Note that the `#include`d files do not become additional source units; they are Source units (such as files) are grouped into _translation units_, and each translation unit will produce a single _module_ when compiled. While the source units are all preprocessed and parsed independently, semantic checking is applied to a translation unit as a whole. -One source file in a translation unit may freely refer to declarations in another translation unit without any need for forward declarations. For example: +One source file in a translation unit may freely refer to declarations in another source file from the same translation unit without any need for forward declarations. For example: ```hlsl // A.slang |