diff options
| author | Charles Harris <charlesr.harris@gmail.com> | 2019-01-08 11:35:44 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-01-08 11:35:44 -0700 |
| commit | 4d0732220ee56fd251665c43b6d43272ad5edef6 (patch) | |
| tree | f0e889824068203e3ead18dbb0ae5241ae7e9758 /doc | |
| parent | e8918143bce960e4f1220a2a210edc2c0d7799d7 (diff) | |
| parent | f54f39f8db70b902b2d91512aee6af19625159a4 (diff) | |
| download | numpy-4d0732220ee56fd251665c43b6d43272ad5edef6.tar.gz | |
Merge pull request #12677 from ahaldane/fix_more_uint_aln
MAINT: Further fixups to uint alignment checks
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/source/reference/alignment.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/source/reference/alignment.rst b/doc/source/reference/alignment.rst index b182a1e7b..ebc8f353c 100644 --- a/doc/source/reference/alignment.rst +++ b/doc/source/reference/alignment.rst @@ -97,7 +97,7 @@ Here is how the variables above are used: Note that the strided-copy and strided-cast code are deeply intertwined and so any arrays being processed by them must be both uint and true aligned, even -though te copy-code only needs uint alignment and the cast code only true +though the copy-code only needs uint alignment and the cast code only true alignment. If there is ever a big rewrite of this code it would be good to allow them to use different alignments. |