summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMatti Picus <matti.picus@gmail.com>2021-12-16 00:51:00 -0700
committerGitHub <noreply@github.com>2021-12-16 00:51:00 -0700
commit8f2acc9b44bdf27b8dca417a87d34d0564a52a09 (patch)
tree3cf9f0b911b0b6c96685d3b84fcde15ebab53500
parent1eb2f2e8e05b4b479a1a6b3d1e617be48eb175f9 (diff)
parent71052afe5c7d54c98811f4eab17c42f1b1bcca6c (diff)
downloadnumpy-8f2acc9b44bdf27b8dca417a87d34d0564a52a09.tar.gz
Merge pull request #20591 from mataya88/main
removed two redundant '\\' typos
-rw-r--r--doc/source/user/basics.types.rst4
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