From 3c7273d5329dd9f5ce2b7d9ca48cd8872a2d41c9 Mon Sep 17 00:00:00 2001 From: cheatfate Date: Tue, 29 May 2018 02:38:53 +0300 Subject: [PATCH] Update README. --- README.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 60e34a7..82d26b5 100644 --- a/README.md +++ b/README.md @@ -16,10 +16,14 @@ Asyncdispatch hard fork. 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). - To resolve this issue introduced unified callback type `CallbackFunc`, which is - looks like `CallbackFunc* = proc (arg: pointer = nil) {.gcsafe.}`. Also one more type is introduced for callback storage is `AsyncCallback`. - + To resolve this issue introduced unified callback type `CallbackFunc`, which is looks like + ```nim + type + CallbackFunc* = proc (arg: pointer = nil) {.gcsafe.} ``` + Also one more type is introduced for callback storage is `AsyncCallback`. + + ```nim type AsyncCallback* = object function*: CallbackFunc