Skip to content

Instantly share code, notes, and snippets.

@zevv
zevv / gist:66fd5b6abb0f9b7c80c99d470ef75bf1
Created July 27, 2019 12:53
State of the nim async stdlib.md
# TL;DR
There are two incompatible async I/O libraries available for Nim, which is not a good thing given the fundamental layer at which these libraries operate. The risk is that this might split the library ecosystem. I hope to find a resolution for this situation that makes everybody happy.
# Background
Over the last few weeks/months I have seen a number of discussions on the Nim forum and the #nim IRC channel about the state of the Nim async library. After speaking with some (but not all!) of the people involved I figured it is time to make this into an official discussion to see how this can be resolved and we can move forward.
Here is the back story:

Within an except clause it is possible to access the current exception using the following syntax:

  try:
    # ...
  except IOError as e:
    # Now use "e"
    echo "I/O error: " & e.msg

Keybase proof

I hereby claim:

  • I am zevv on github.
  • I am zevv (https://keybase.io/zevv) on keybase.
  • I have a public key whose fingerprint is F042 F5CD B0A6 EC6A CB80 A829 CACD A4B5 4202 FA2F

To claim this, I am signing this object:

test 123