diff options
| author | Muataz Attaia <81917324+mataya88@users.noreply.github.com> | 2021-12-16 00:40:32 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-12-16 00:40:32 +0300 |
| commit | 71052afe5c7d54c98811f4eab17c42f1b1bcca6c (patch) | |
| tree | f052fe46738c6cf96e90694b50ca190c92b9d561 | |
| parent | 06e37a3e6e48f06a3ff4010b4ad88e4b001184fb (diff) | |
| download | numpy-71052afe5c7d54c98811f4eab17c42f1b1bcca6c.tar.gz | |
removed two redundant '\\' typos
| -rw-r--r-- | doc/source/user/basics.types.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/source/user/basics.types.rst b/doc/source/user/basics.types.rst index 354f003fb..fb36af46c 100644 --- a/doc/source/user/basics.types.rst +++ b/doc/source/user/basics.types.rst @@ -258,8 +258,8 @@ compiler's ``long double`` available as ``np.longdouble`` (and numpy provides with ``np.finfo(np.longdouble)``. NumPy does not provide a dtype with more precision than C's -``long double``\\; in particular, the 128-bit IEEE quad precision -data type (FORTRAN's ``REAL*16``\\) is not available. +``long double``; in particular, the 128-bit IEEE quad precision +data type (FORTRAN's ``REAL*16``) is not available. For efficient memory alignment, ``np.longdouble`` is usually stored padded with zero bits, either to 96 or 128 bits. Which is more efficient |