Simon Brunel

`label` is private and will not be exposed as-is since I don't want to give full control over our internals and be locked with implementation details. `callbacks` in the options...

> Would an addition like `value_or()` be useful for the library? I'm not sure it would be really useful since, as @pwuertz mentioned, the `.wait()` API is probably not a...

Hi @durkmurder, It looks similar to #20 but with a different use case. I also find myself doing this check a lot and I agree that we may need to...

> Folly supports via() in different way ... Folly `.via()` seems to define *where* (thread) the callback is executed, not *if* (`QPointer`) the callback should be executed. Your example is...

Your first example doesn't reflect the *where* because the `then()` callback is a lambda. Do you have another example maybe that would help to understand better your use case? Option...

@pwuertz @dpurgin any thoughts?

Ok, I fully get it now, thanks! So indeed, option 4 doesn't address the *where* part. Option 5 would work but I agree that it requires more code (though I...

Still thinking about option 5: it's very close to 3.1 and to me, it's less error prone than 3.2 because it doesn't need to `unbind()` before returning the promise. ```cpp...

Hi guys! Thank you for your feedback, it's really interesting to learn about how you use QtPromise. And sorry for the late reply, I'm currently focused on something else far...

@Adphi Thank you :) What do you mean exactly by "... support QPromise exposition to QML"? I started writing a QML wrapper allowing to use the same functionalities in JavaScript:...