Commit 3f7a0302 authored by scoder's avatar scoder Committed by GitHub

Merge pull request #2495 from luzpaz/misc-typos

Misc. typos
parents e5a3d9d6 7bda96a2
...@@ -7899,7 +7899,7 @@ class ListNode(SequenceNode): ...@@ -7899,7 +7899,7 @@ class ListNode(SequenceNode):
return () return ()
def infer_type(self, env): def infer_type(self, env):
# TOOD: Infer non-object list arrays. # TODO: Infer non-object list arrays.
return list_type return list_type
def analyse_expressions(self, env): def analyse_expressions(self, env):
...@@ -8564,7 +8564,7 @@ class DictNode(ExprNode): ...@@ -8564,7 +8564,7 @@ class DictNode(ExprNode):
return () return ()
def infer_type(self, env): def infer_type(self, env):
# TOOD: Infer struct constructors. # TODO: Infer struct constructors.
return dict_type return dict_type
def analyse_types(self, env): def analyse_types(self, env):
......
...@@ -594,9 +594,9 @@ class MemoryViewSliceType(PyrexType): ...@@ -594,9 +594,9 @@ class MemoryViewSliceType(PyrexType):
the packing specifiers specify how the array elements are layed-out the packing specifiers specify how the array elements are layed-out
in memory. in memory.
'contig' -- The data are contiguous in memory along this dimension. 'contig' -- The data is contiguous in memory along this dimension.
At most one dimension may be specified as 'contig'. At most one dimension may be specified as 'contig'.
'strided' -- The data aren't contiguous along this dimenison. 'strided' -- The data isn't contiguous along this dimension.
'follow' -- Used for C/Fortran contiguous arrays, a 'follow' dimension 'follow' -- Used for C/Fortran contiguous arrays, a 'follow' dimension
has its stride automatically computed from extents of the other has its stride automatically computed from extents of the other
dimensions to ensure C or Fortran memory layout. dimensions to ensure C or Fortran memory layout.
......
...@@ -2486,7 +2486,7 @@ class PyCont(ExecutionControlCommandBase): ...@@ -2486,7 +2486,7 @@ class PyCont(ExecutionControlCommandBase):
def _pointervalue(gdbval): def _pointervalue(gdbval):
""" """
Return the value of the pionter as a Python int. Return the value of the pointer as a Python int.
gdbval.type must be a pointer type gdbval.type must be a pointer type
""" """
......
...@@ -361,7 +361,7 @@ Here, ``Py_ssize_t``:: ...@@ -361,7 +361,7 @@ Here, ``Py_ssize_t``::
cdef int pop(self): cdef int pop(self):
return <Py_ssize_t>cqueue.queue_pop_head(self._c_queue) return <Py_ssize_t>cqueue.queue_pop_head(self._c_queue)
Normally, in C, we risk loosing data when we convert a larger integer type Normally, in C, we risk losing data when we convert a larger integer type
to a smaller integer type without checking the boundaries, and ``Py_ssize_t`` to a smaller integer type without checking the boundaries, and ``Py_ssize_t``
may be a larger type than ``int``. But since we control how values are added may be a larger type than ``int``. But since we control how values are added
to the queue, we already know that all values that are in the queue fit into to the queue, we already know that all values that are in the queue fit into
......
...@@ -640,7 +640,7 @@ You can call the function in a Cython file in the following way: ...@@ -640,7 +640,7 @@ You can call the function in a Cython file in the following way:
Several things to note: Several things to note:
- ``::1`` requests a C contiguous view, and fails if the buffer is not C contiguous. - ``::1`` requests a C contiguous view, and fails if the buffer is not C contiguous.
See :ref:`c_and_fortran_contiguous_memoryviews`. See :ref:`c_and_fortran_contiguous_memoryviews`.
- ``&arr_memview[0]`` can be understood as 'the adress of the first element of the - ``&arr_memview[0]`` can be understood as 'the address of the first element of the
memoryview'. For contiguous arrays, this is equivalent to the memoryview'. For contiguous arrays, this is equivalent to the
start address of the flat memory buffer. start address of the flat memory buffer.
- ``arr_memview.shape[0]`` could have been replaced by ``arr_memview.size``, - ``arr_memview.shape[0]`` could have been replaced by ``arr_memview.size``,
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment