Also, do we want to allow a re-assignment after a move to re-use the object?
Just some food for thought, have you explored extending Option to capture
this?
Optionvectorint v {1, 2, 3, 4};
foo(v.move());
v.isSome(); // false
v = {1, 2, 3, 4};
v.isSome() // true
On Wed, Jun 17, 2015 at 7:19 AM,
Hi All,
I have now filed a Jira ticket (MESOS-2884)[1] and created a couple of
RRs[2] along the lines of the suggestions provided by Ian and Jie.
There is one difference though. Instead of creating a LinuxIsolator class,
I added the `int namespaces()` directly to Isolator class. By default, it
+1 for 1. “treat it like a deleted pointer”
On Jun 12, 2015, at 4:21 PM, Alexander Rojas alexan...@mesosphere.io wrote:
Hey guys, there have been questions on how to deal with std::move in the
code. Right now our style guide says nothing about it, but there is no
consensus in the
GitHub user kensipe opened a pull request:
https://github.com/apache/mesos/pull/46
fixed broken 404 doc link for torque on mesos
It is unclear if Torque is an active project... I can remove the torque
docs if it is preferred. However the doc links for torque resulted in a 404
Hi 宗志,
i suggest you reference a paper: Lithe: Enabling Efficient Composition of
Parallel Libraries
2015-06-11 20:09 GMT+08:00 baotiao baot...@gmail.com:
Hi People
I am interested in libproces, and we know libprocess was wrote according
Lithe.
I have some questions about the theory Lithe
