mirror of
https://github.com/nim-lang/Nim.git
synced 2026-01-02 03:02:31 +00:00
02f73120ae
Reworked closureiter transformation.
- Convolutedly nested finallies should cause no problems now.
- CurrentException state now follows nim runtime rules (pushes and pops
appropriately), and mimics normal code, which is somewhat buggy, see
#25031
- Previously state optimization (removing empty states or extra jumps)
missed some opportunities, I've reimplemented it to do everything
possible to optimize the states. At this point any extra states or jumps
should be considered a bug.
The resulting codegen (compiled binaries) is also slightly smaller.
**BUT:**
- I had to change C++ reraising logic, see expt.nim. Because with
closure iters `currentException` is not always in sync with C++'s notion
of current exception. From my tests and understanding of C++ runtime
there should not be any problems, but I'm only 99% sure :)
- I've reused `nfNoRewrite` flag in one specific case during the
transformation. This flag is also used in term-rewriting logic. Again,
99% sure, these 2 scenarios will never intersect.
(cherry picked from commit 36f8cefa85)
28 lines
463 B
Nim
28 lines
463 B
Nim
import std/asyncdispatch
|
|
|
|
proc errval {.async.} =
|
|
raise newException(ValueError, "err")
|
|
|
|
proc err {.async.} =
|
|
try:
|
|
doAssert false
|
|
finally:
|
|
echo "finally"
|
|
# removing the following code will propagate the AssertionDefect
|
|
try:
|
|
await errval()
|
|
except ValueError:
|
|
echo "valueError"
|
|
|
|
proc main {.async.} =
|
|
let errFut = err()
|
|
await errFut
|
|
|
|
var ok = false
|
|
try:
|
|
waitFor main()
|
|
except AssertionDefect:
|
|
ok = true
|
|
|
|
doAssert(ok)
|