logos-storage/nim-chronos
1
0
Fork 0
mirror of https://github.com/logos-storage/nim-chronos.git synced 2026-01-07 16:03:09 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update README.

Browse Source
This commit is contained in:
cheatfate 2018-05-29 02:37:06 +03:00
parent 5529fc4669
commit edcc628b30
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@ -8,10 +8,10 @@ Asyncdispatch hard fork.
1. Unified callback type `CallbackFunc`. 1. Unified callback type `CallbackFunc`.
Current version of asyncdispatch uses many types of callbacks. Current version of asyncdispatch uses many types of callbacks.
`proc ()` used in callSoon() callbacks and Future[T] completion callbacks. - `proc ()` used in callSoon() callbacks and Future[T] completion callbacks.
`proc (fut: Future[T])` used in Future[T] completion callbacks. - `proc (fut: Future[T])` used in Future[T] completion callbacks.
`proc (fd: AsyncFD, bytesTransferred: Dword, errcode: OSErrorCode)` used in Windows IO completion callbacks. - `proc (fd: AsyncFD, bytesTransferred: Dword, errcode: OSErrorCode)` used in Windows IO completion callbacks.
`proc (fd: AsyncFD): bool` used in Unix IO events callbacks. - `proc (fd: AsyncFD): bool` used in Unix IO events callbacks.
Such a number of different types creates big problems in the storage, processing and interaction between callbacks. Lack of ability to pass custom user data to Such a number of different types creates big problems in the storage, processing and interaction between callbacks. Lack of ability to pass custom user data to
callback also creates difficulties and inefficiency, to pass custom user-defined data you need to use closures (one more allocation). callback also creates difficulties and inefficiency, to pass custom user-defined data you need to use closures (one more allocation).