Ability to set a NimNode's lineinfo

[dom96]

The only way to set this information is via newNimNode, but a lot of the time I have a node that was created via newCall or some other convenience function. These functions don't allow me to specify the line info information so it would be nice to be able to assign it after the fact.

[dom96]

Reminder for myself (or others if they wish to take this on): once this issue is fixed go through asyncmacro and give every new node line info, especially here.

[dom96]

Another request:

Please expose something that will allow me to make these unwieldy async errors clearer. Take a look at this:

Traceback (most recent call last)
server.nim(213)          server
asyncdispatch.nim(1081)  waitFor
asyncdispatch.nim(1072)  poll
asyncdispatch.nim(1242)  cb
asyncfutures.nim(118)    complete
asyncdispatch.nim(1387)  :anonymous
asyncfutures.nim(118)    complete
asyncmacro.nim(34)       cb
asyncmacro.nim(334)      sendIter
asyncfutures.nim(118)    complete
asyncmacro.nim(34)       cb
asyncmacro.nim(334)      verifyWebsocketRequestIter
asyncfutures.nim(109)    complete
asyncmacro.nim(50)       cb
asyncfutures.nim(156)    fail
asyncmacro.nim(50)       cb
asyncfutures.nim(156)    fail
asyncmacro.nim(50)       cb
asyncfutures.nim(156)    fail
asyncfutures.nim(322)    :anonymous
Error: unhandled exception: index out of bounds
  onRequest's lead up to read of failed Future:
    Traceback (most recent call last)
    server.nim(213)          server
    asyncdispatch.nim(1081)  waitFor
    asyncdispatch.nim(1072)  poll
    asyncdispatch.nim(1242)  cb
    asyncfutures.nim(118)    complete
    asyncdispatch.nim(1387)  :anonymous
    asyncfutures.nim(118)    complete
    asyncmacro.nim(34)       cb
    asyncmacro.nim(334)      sendIter
    asyncfutures.nim(118)    complete
    asyncmacro.nim(34)       cb
    asyncmacro.nim(334)      verifyWebsocketRequestIter
    asyncfutures.nim(109)    complete
    asyncmacro.nim(34)       cb
    **server.nim(163)          onRequestIter**
    system.nim(2628)         sysFatal
  cb's lead up to read of failed Future:
    Traceback (most recent call last)
    server.nim(213)          server
    asyncdispatch.nim(1081)  waitFor
    asyncdispatch.nim(1072)  poll
    asyncdispatch.nim(1242)  cb
    asyncfutures.nim(118)    complete
    asyncdispatch.nim(1387)  :anonymous
    asyncfutures.nim(118)    complete
    asyncmacro.nim(34)       cb
    asyncmacro.nim(334)      sendIter
    asyncfutures.nim(118)    complete
    asyncmacro.nim(34)       cb
    asyncmacro.nim(334)      verifyWebsocketRequestIter
    asyncfutures.nim(109)    complete
    asyncmacro.nim(50)       cb
    asyncfutures.nim(156)    fail
    asyncmacro.nim(34)       cb
    asyncmacro.nim           cbIter
    asyncfutures.nim(220)    read
  processClient's lead up to read of failed Future:
    Traceback (most recent call last)
    server.nim(213)          server
    asyncdispatch.nim(1081)  waitFor
    asyncdispatch.nim(1072)  poll
    asyncdispatch.nim(1242)  cb
    asyncfutures.nim(118)    complete
    asyncdispatch.nim(1387)  :anonymous
    asyncfutures.nim(118)    complete
    asyncmacro.nim(34)       cb
    asyncmacro.nim(334)      sendIter
    asyncfutures.nim(118)    complete
    asyncmacro.nim(34)       cb
    asyncmacro.nim(334)      verifyWebsocketRequestIter
    asyncfutures.nim(109)    complete
    asyncmacro.nim(50)       cb
    asyncfutures.nim(156)    fail
    asyncmacro.nim(50)       cb
    asyncfutures.nim(156)    fail
    asyncmacro.nim(34)       cb
    asyncmacro.nim           processClientIter
    asyncfutures.nim(220)    read [Exception]

I emphasised the "useful" information using asterisks. There is far too much noise in these exceptions and it would be nice to combine them instead of having multiple stack traces.

[7sDream]

Any progress?