diff options
| author | cheneym2 <acheney@nvidia.com> | 2024-10-23 23:34:49 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-10-24 11:34:49 +0800 |
| commit | fb50c032959d0f21579e8a6e1a0ab7141c7fbb97 (patch) | |
| tree | 5fabb7e3ca848c3f87bb6d23031a859d170f46c8 /docs/cpu-target.md | |
| parent | a0bea07503c68160ad2e88986ba98cfc2161bdff (diff) | |
Fix a few documentation typos (#5396)
Diffstat (limited to 'docs/cpu-target.md')
| -rw-r--r-- | docs/cpu-target.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/cpu-target.md b/docs/cpu-target.md index 76226a2b8..46e33c0c2 100644 --- a/docs/cpu-target.md +++ b/docs/cpu-target.md @@ -616,7 +616,7 @@ Vector<float, 3> defValue = {}; // Zero initialize such that read access values.at(3).x = 10; ``` -Note that '[] 'would be turned into the `at` function, which takes the default value as a paramter provided by the caller. If this is then written to then only the defValue is corrupted. Even this mechanism not be quite right, because if we write and then read again from the out of bounds reference in HLSL we may expect that 0 is returned, whereas here we get the value that was last written. +Note that '[] 'would be turned into the `at` function, which takes the default value as a parameter provided by the caller. If this is then written to then only the defValue is corrupted. Even this mechanism not be quite right, because if we write and then read again from the out of bounds reference in HLSL we may expect that 0 is returned, whereas here we get the value that was last written. ## <a id="zero-index"/>Zero index bound checking |
