Github user aaronjwood commented on the issue:
https://github.com/apache/mesos/pull/157
I might be misunderstanding things but why can we not do this? I see it
being done here
https://github.com/apache/mesos/blob/master/3rdparty/libprocess/src/http.cpp#L1001
If we make the `Promise` local like it is in this patch, pass its address
into the tuple via the copy constructor (that should be the copy constructor
getting called, right?) so that it takes a copy and doesn't rely on an actual
address from the stack, and return the future in the same way as the example
above, would that not work? Even though the `Promise` is local to the stack,
when we return `Future` shouldn't it be a copy of what's needed underneath?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
