status-im
/
nimbus-eth1
mirror of https://github.com/status-im/nimbus-eth1.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Using raises pragma with logging really makes no sense currently but okay...

This commit is contained in:
kdeme 2019-11-05 14:18:07 +01:00 committed by zah
parent 0f299842e1
commit cf725062e9
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
wrappers/libnimbus.nim
View File

@ -247,7 +247,7 @@ proc nimbus_new_keypair(): cstring {.exportc, raises: [].} =
result = ""
proc nimbus_add_keypair(privateKey: ptr byte):
cstring {.exportc, raises: [OSError, IOError].} =
cstring {.exportc, raises: [OSError, IOError, ValueError].} =
## It is important that the caller makes a copy of the returned cstring before
## doing any other API calls. This might not hold for all types of GC.
doAssert(not privateKey.isNil, "Passed a null pointer as privateKey")
@ -270,7 +270,7 @@ proc nimbus_delete_keypair(id: cstring): bool {.exportc, raises: [].} =
result = whisperKeys.asymKeys.take($id, unneeded)
proc nimbus_get_private_key(id: cstring, privateKey: ptr PrivateKey):
bool {.exportc, raises: [OSError, IOError].} =
bool {.exportc, raises: [OSError, IOError, ValueError].} =
doAssert(not id.isNil, "Key id cannot be nil")
doAssert(not privateKey.isNil, "Passed a null pointer as privateKey")