- 15 Jul, 2018 1 commit
-
-
Kenton Varda authored
Just like `Promise<Promise<T>>` reduces to `Promise<T>`, we should be able to reduce `Promise<RemotePromise<T>>`. Moreover, this reduction should support pipelining, hence the reduced type should itself be `RemotePromise<T>`. Fixes #341
-
- 18 Apr, 2018 2 commits
-
-
Harris Hancock authored
-
Kenton Varda authored
This is necessary when someone other than the promise owner might need to destroy the state a promise is operating on. It comes up when implementing pumpTo() for userland pipes -- cancelling the pump needs to cancel any writes currently passing through the pipe.
-
- 11 Jan, 2018 1 commit
-
-
Kenton Varda authored
@kloepper pointed out a while back that every compiler you've ever heard of supports this. Plus, it's more concise, it's not prone to copy-paste errors, and it looks nicer. At the time I wanted to remain consistent and I didn't feel like spending the time to update all my existing code. But, every time I've added a new header since I've cursed the include guard, so I finally broke down and changed it.
-
- 25 Oct, 2017 1 commit
-
-
Kenton Varda authored
Fixes #286.
-
- 24 Oct, 2017 1 commit
-
-
Kenton Varda authored
I intended to do this, like, 4 years ago.
-
- 22 Sep, 2017 1 commit
-
-
Kenton Varda authored
-
- 21 Sep, 2017 1 commit
-
-
Kenton Varda authored
These are useful in unit tests. Often, some tasks have been queued, and we want to test that a particular thing happens or doesn't happen as a result of those tasks, without actually waiting on any specific promise. We need a way to run the event queue until it is empty. For that, we add WaitScope::poll(). Or, sometimes, we want to check if a specific promise is (or is not!) resolved as a result of the tasks that have been queued so far, but we may not want to actulaly wait() on it for a couple reasons: - We may actually want to verify that the promise is *not* resolved by tasks so far. wait()ing on it would be expected to deadlock. - We may expect the promise to resolve, but would prefer not to deadlock if it doesn't resolve (we'd rather fail fast). For this, we add Promise::poll(). There are lots of tests I've written which could be simplified by this, but for now I'm not refactoring any existing tests. Note that adding these (particularly Promise::poll()) required updating the async framework a bit, in that this is the first case where PromiseNode::onReady() might be called multiple times, or might be canceled without destroying the PromiseNode entirely. Luckily this was not hard to account for. (We still have the rule that get() can only be called once, though.)
-
- 07 Oct, 2016 1 commit
-
-
Kenton Varda authored
-
- 01 Feb, 2016 1 commit
-
-
Kenton Varda authored
This is largely motivated by the fact that Clang currently miscompiles `.then([](auto){})`: https://llvm.org/bugs/show_bug.cgi?id=24989
-
- 25 Apr, 2015 1 commit
-
-
David Renshaw authored
-
- 19 Feb, 2015 1 commit
-
-
Kenton Varda authored
- Promise<T>::catch_() method which is equivalent to then() but you only specify an error handler; the non-error continuation is the identity function. - kj::evalNow() function which synchronously calls a function and returns a promise for the result, or a broken promise if the function threw an exception. This is convenient for making sure exceptions get pushed into the promise chain. - KJ_WARN_UNUSED_RESULT on various methods that return promises.
-
- 29 Dec, 2014 1 commit
-
-
Kenton Varda authored
-
- 09 Dec, 2014 1 commit
-
-
Kenton Varda authored
This is not currently used, but eventually we'll use this to support efficient inter-thread messaging. That said, I've decided that inter-thread messaging is complicated and I don't want to work on it right now.
-
- 22 Nov, 2014 1 commit
-
-
Kenton Varda authored
This prevents the compiler from reporting warnings in these headers while compiling application code. Hopefully this will stem the never-ending stream of complaints from people who enable pedantic warnings.
-
- 20 Jun, 2014 1 commit
-
-
Kenton Varda authored
For portions currently copyright by Kenton (most of it), transfer copyright to Sandstorm Development Group, Inc. (Kenton's company). The license change is practically meaningless, as MIT and BSD 2-clause are legally equivalent. However, the BSD 2-clause license is sometimes confused for its ugly siblings, BSD 3-clause and BSD 4-clause. The MIT license is more immediately recognizeable for what it is. Rémy Blank and Jason Choy (the two non-trivial contributors) are on record as approving this change: https://groups.google.com/d/msg/capnproto/xXDd2HUOCcc/gbe_COIuXKYJ
-
- 10 Dec, 2013 1 commit
-
-
Kenton Varda authored
-
- 07 Dec, 2013 1 commit
-
-
Kenton Varda authored
-
- 06 Dec, 2013 1 commit
-
-
Kenton Varda authored
-
- 05 Dec, 2013 3 commits
-
-
Kenton Varda authored
Make all Promise methods consistently consume the promise (returning a new promise when it makes sense), rename daemonize -> detach, and make eagerlyEvaluate() require an error handler (this caught several places where I forgot to use one).
-
Kenton Varda authored
-
Kenton Varda authored
-
- 04 Dec, 2013 2 commits
-
-
Kenton Varda authored
-
Kenton Varda authored
Overhaul the way EventLoop is specialized so that it's possible to hook up to an existing event loop infrastructure that is not KJ-aware. This also makes the async IO API more dependency-injection-friendly.
-
- 30 Nov, 2013 4 commits
-
-
Kenton Varda authored
-
Kenton Varda authored
-
Kenton Varda authored
-
Kenton Varda authored
-
- 28 Nov, 2013 2 commits
-
-
Kenton Varda authored
-
Kenton Varda authored
Revamp concurrency model, part 1: EventLoop no longer allows cross-thread event queuing, simplifying many things. Capability clients are no longer thread-safe, so they don't have to be so const. In the future, explicit ways to communicate between threads will be re-added, but threads will be treated more like separate vats that just happen to have a particularly fat pipe. Upcoming: Remove mutexes.
-
- 26 Nov, 2013 2 commits
-
-
Kenton Varda authored
Make EventLoop current when constructed, so that you can use the Promise methods even when the loop hasn't actually started yet.
-
Kenton Varda authored
-
- 22 Nov, 2013 1 commit
-
-
Kenton Varda authored
Implement exclusive promise joining: Join two Promise<T>s to create a Promise that resolves when either input resolves.
-
- 19 Nov, 2013 1 commit
-
-
Kenton Varda authored
-
- 15 Nov, 2013 3 commits
-
-
Kenton Varda authored
-
Kenton Varda authored
-
Kenton Varda authored
-
- 14 Nov, 2013 2 commits
-
-
Kenton Varda authored
-
Kenton Varda authored
-
- 02 Nov, 2013 1 commit
-
-
Kenton Varda authored
-