Skip to content

Commit 612f2af

Browse files
committed
address review: apply rest of suggestions
1 parent 0df61c9 commit 612f2af

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

peps/pep-0812.rst

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -202,10 +202,10 @@ Simplicity is a goal, but most importantly for the end user, not implementers
202202
of the complex arithmetic.
203203

204204

205-
Upcoming C2y standard abandons [8]_ the imaginary type
206-
------------------------------------------------------
205+
Upcoming C2y standard abandons the imaginary type
206+
-------------------------------------------------
207207

208-
That might be viewed as a failure of the new approach: no compiler from major
208+
That [8]_ might be viewed as a failure of the new approach: no compiler from major
209209
players had a correct implementation of the C99 Annex G.
210210

211211
On the other hand, this might be also viewed as an indication of poor adoption of
@@ -404,7 +404,7 @@ from Python objects and do arithmetic with some external library (like the GNU
404404
GSL), then import back.
405405
406406
407-
It's Not Magic
407+
It's not Magic
408408
==============
409409
410410
New arithmetic rules correct some more examples, where using known analytic
@@ -547,9 +547,9 @@ explain then a dedicated concept of imaginary numbers as a subtype of complex.
547547
Open Issues
548548
===========
549549
550-
The PEP doesn't expose new subtype as a builtin, say ``imaginary``, but maybe
550+
The PEP doesn't expose a new subtype as a builtin, say ``imaginary``, but maybe
551551
we should? This looks redundant, as all imaginary values could be obtained by
552-
scaling imaginary unit, i.e. ``imaginary(x) == float(x)*1j``.
552+
scaling the imaginary unit, i.e. ``imaginary(x) == float(x)*1j``.
553553
554554
555555
Acknowledgements

0 commit comments

Comments
 (0)