Explain Different Approaches to Asynchronous Calls about mistkit HOT 3 CLOSED

Hey @mickeyl

You are correct you need to handle the mainloop somehow.
Would it be helpful to add something like this to the documentation?

database.perform(request: request) { result in
    do {
        try print(result.get().records.information)
    } catch {
        print("an error occured: \(error)")
        return
    }
    CFRunLoopStop(CFRunLoopGetMain())
}
CFRunLoopRun()

My worry is that this is specific for a command-line application as opposed to a server-side application. I'd prefer to let the user handle the async call in their own manner (i.e. EventLoopFuture, DispatchSemaphore, DispatchGroup, RunLoop etc...). I assume this is command-line application, correct?

Regardless, let me know if this fixes your issue.

from mistkit.

Thanks a lot, adding the runloop made it work for me. I think at least a quick side remark that highlights the necessity for a runloop (which, yes, is a given for server-side apps, but as you guessed I'm working on a command-line tool) would be helpful.

from mistkit.

I'm going to reopen the issue so I keep note of needing to amend the documentation. Thanks @mickeyl

from mistkit.