Error -> Defect for defects (#13908)

* Error -> Defect for defects

The distinction between Error and Defect is subjective,
context-dependent and somewhat arbitrary, so when looking at an
exception, it's hard to guess what it is - this happens often when
looking at a `raises` list _without_ opening the corresponding
definition and digging through layers of inheritance.

With the help of a little consistency in naming, it's at least possible
to start disentangling the two error types and the standard lib can set
a good example here.
This commit is contained in:
Jacek Sieka
2020-04-28 19:56:01 +02:00
committed by GitHub
parent cd9af6b804
commit 7d6cbf290a
92 changed files with 323 additions and 300 deletions

View File

@@ -1,5 +1,5 @@
discard """
outputsub: "Error: unhandled exception: FPU operation caused an overflow [FloatOverflowError]"
outputsub: "Error: unhandled exception: FPU operation caused an overflow [FloatOverflowDefect]"
exitcode: "1"
"""
# Test new floating point exceptions

View File

@@ -1,5 +1,5 @@
discard """
outputsub: "Error: unhandled exception: FPU operation caused a NaN result [FloatInvalidOpError]"
outputsub: "Error: unhandled exception: FPU operation caused a NaN result [FloatInvalidOpDefect]"
exitcode: "1"
"""
# Test new floating point exceptions