mirror of
https://github.com/nim-lang/Nim.git
synced 2025-12-30 09:54:49 +00:00
* 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.
40 lines
933 B
Nim
40 lines
933 B
Nim
discard """
|
|
cmd: "nim $target $options --excessiveStackTrace:off $file"
|
|
output: '''true'''
|
|
"""
|
|
|
|
const expected = """
|
|
tassert_c.nim(35) tassert_c
|
|
tassert_c.nim(34) foo
|
|
assertions.nim(29) failedAssertImpl
|
|
assertions.nim(22) raiseAssert
|
|
fatal.nim(49) sysFatal"""
|
|
|
|
proc tmatch(x, p: string): bool =
|
|
var i = 0
|
|
var k = 0
|
|
while i < p.len:
|
|
if p[i] == '*':
|
|
let oldk = k
|
|
while k < x.len and x[k] in {'0'..'9'}: inc k
|
|
# no digit skipped?
|
|
if oldk == k: return false
|
|
inc i
|
|
elif k < x.len and p[i] == x[k]:
|
|
inc i
|
|
inc k
|
|
else:
|
|
return false
|
|
while k < x.len and x[k] in {' ', '\L', '\C'}: inc k
|
|
result = i >= p.len and k >= x.len
|
|
|
|
|
|
try:
|
|
proc foo() =
|
|
assert(false)
|
|
foo()
|
|
except AssertionDefect:
|
|
let e = getCurrentException()
|
|
let trace = e.getStackTrace
|
|
if tmatch(trace, expected): echo true else: echo "wrong trace:\n" & trace
|