[
https://issues.apache.org/jira/browse/MESOS-4152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15082185#comment-15082185
]
Benjamin Mahler commented on MESOS-4152:
----------------------------------------
To be accurate, it doesn't prevent the caller from *requesting a discard*.
Preventing callers from requesting a discard (e.g. at compile time by
introducing a Future w/o {{discard()}}, or at run-time by providing a means to
check for discard support) is orthogonal to this issue. I say that because,
even if discard was a valid way to use process::Queue, when the caller requests
a discard it must not assume the discard takes place. The caller must always
use the transition state of the future to determine whether the future was
discarded.
> discarding a Future from process::Queue loses elements
> ------------------------------------------------------
>
> Key: MESOS-4152
> URL: https://issues.apache.org/jira/browse/MESOS-4152
> Project: Mesos
> Issue Type: Bug
> Components: libprocess
> Reporter: James Peach
>
> If you discard the Future you get from {{process::Queue}} the next element
> inserted into the queue will be lost.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
