Searched refs:consensus (Results 1 – 25 of 34) sorted by relevance
12
428 val consensus = if (decision != null) { in <lambda>() constant432 atomicOp.consensus // consult with current decision status like in Harris DCSS in <lambda>()435 … consensus === NO_DECISION -> atomicOp // desc.onPrepare returned null -> start doing atomic op in <lambda>()436 … consensus == null -> desc.updatedNext(affected, next) // move forward if consensus on success in <lambda>()
61 val consensus: Any? get() = _consensus.value constant in kotlinx.coroutines.internal.AtomicOp
31 likely-community-consensus requirements (as apply to all patch approvals) can91 reviewers can request an RFC achieving consensus before proceeding with code162 Our goal is to ensure community consensus around design decisions and165 consensus exists. If you're not familiar enough with the community to know,
149 Inclusion must reach consensus in the RFC by the community and the approval of208 #. There must be enough consensus on the list that removal is warranted, and no
347 .. _discuss the change/gather consensus:368 idea to get consensus with the development community before you start working on410 consensus on what the end goal of the change is.428 sure to first `discuss the change/gather consensus`_ then ask about the best way538 * Once the RFC reaches consensus, update the CMake toolchain version checks as
84 …LVM Security Group members should discuss the matter and try to come to consensus; failing this, t…
30 - There is a consensus on the semantics/instruction set of VP.
128 The consensus within the community seems to be that at least some acronyms are
33 up for discussion, to object to or to praise. Ideally, we find consensus for36 If there is no obvious consensus, a maintainer who's knowledgeable in the
202 # but there is consensus that it should be.
393 .. _discuss the change/gather consensus:414 idea to get consensus with the development community before you start working on456 consensus on what the end goal of the change is.474 sure to first `discuss the change/gather consensus`_ then ask about the best way
160 NOTE: There is no clear consensus on the maximum latency that the scheduler
84 # Note: added Tatweel to these, since that seems to be the current consensus.
36 characters with ordinals 128-255. While there is no consensus on this subject
113 revised until the community reaches a consensus, either accepting or rejecting128 consensus within the community and documenting dissenting opinions.
263 consensus (yet) on whether and how to do range tests. See :pep:`275` for
900 dnl general consensus is that you shouldn't need this ability.
335 consensus (yet) on whether and how to do range tests. See :pep:`275` for
639 responsible for building consensus within the community and documenting
907 dnl general consensus is that you shouldn't need this ability.
924 responsible for building consensus within the community and documenting
1116 # From the above it appears that there is a working consensus in
797 # Now we turn to US areas that have diverged from the consensus since 1970.
10466 consensus