Data

Tools

Indexes

Applications

Experiments

Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / cplusplus/concurrency-ts issues and pull requests

#100 - Nothing to "see below" for [shared_]future::get

Issue - State: open - Opened by timsong-cpp over 9 years ago - 6 comments

#99 - 1.3 Table 2: typo in header name <experimental/atomics>

Issue - State: closed - Opened by cubbimew about 10 years ago - 1 comment

#98 - Update to v0.3.2 of the HTML document framework.

Pull Request - State: open - Opened by jyasskin about 10 years ago

#97 - Can is_ready by noexcept

Issue - State: closed - Opened by arturl about 10 years ago - 2 comments

#96 - Add additional headers in Table 1: C++ library headers

Issue - State: closed - Opened by arturl about 10 years ago

#95 - Remove reference in future::share (typo)

Issue - State: closed - Opened by arturl about 10 years ago - 1 comment

#94 - Address comments from Jonathan Wakely

Issue - State: closed - Opened by arturl about 10 years ago - 2 comments

#93 - Typo in 1.3/2 table

Issue - State: closed - Opened by arturl over 10 years ago - 1 comment

#92 - Remove "add the following ..." in the text

Issue - State: closed - Opened by arturl over 10 years ago - 1 comment

#91 - API name missing in 3.2.5?

Issue - State: closed - Opened by arturl over 10 years ago - 1 comment

#90 - Code font for num_threads

Issue - State: closed - Opened by arturl over 10 years ago - 1 comment

#89 - Fix nested Notes

Issue - State: closed - Opened by arturl over 10 years ago - 1 comment

#88 - Remove 'N' from subtitles in Latches and Barriers

Issue - State: closed - Opened by arturl over 10 years ago - 1 comment

#87 - Fix indentation for Latches and Barriers

Issue - State: closed - Opened by arturl over 10 years ago - 2 comments

#86 - LWG: when_all: post condition, "all input futures..." is not a sentence

Issue - State: closed - Opened by arturl over 10 years ago - 1 comment
Labels: LWG_Cologne

#85 - LWG: replace "as if" with "equivalent to"

Issue - State: closed - Opened by arturl over 10 years ago - 1 comment
Labels: LWG_Cologne

#84 - LWG: when_all confusion about sequence and collection

Issue - State: closed - Opened by arturl over 10 years ago - 1 comment
Labels: LWG_Cologne

#82 - LWG: Can you call is_ready() on an invalid future? Remarks are wrong.

Issue - State: closed - Opened by arturl over 10 years ago - 1 comment
Labels: LWG_Cologne

#81 - LWG: Why do we unwrap a future but not a shared future?

Issue - State: closed - Opened by arturl over 10 years ago - 2 comments
Labels: LWG_Cologne

#80 - LWG: "as follows" instead of "defined below".

Issue - State: closed - Opened by arturl over 10 years ago - 1 comment
Labels: LWG_Cologne

#79 - LWG: "callable" vs. "closure"

Issue - State: closed - Opened by arturl over 10 years ago - 1 comment
Labels: LWG_Cologne

#78 - LWG: 2.3p13 "R2" is introduced but not defined

Issue - State: closed - Opened by arturl over 10 years ago
Labels: LWG_Cologne

#77 - LWG: The text in "Returns" in 2.3 belongs to "Effects"

Issue - State: closed - Opened by arturl over 10 years ago - 2 comments
Labels: LWG_Cologne

#76 - LWG: INVOKE(func, *this) needs to move *this

Issue - State: closed - Opened by arturl over 10 years ago - 1 comment
Labels: LWG_Cologne

#75 - LWG: Note in 2.3p11 seems useless

Issue - State: closed - Opened by arturl over 10 years ago - 1 comment
Labels: LWG_Cologne

#74 - LWG: "inner" vs. "outer" futures is confusing

Issue - State: closed - Opened by arturl over 10 years ago - 1 comment
Labels: LWG_Cologne

#73 - LWG: Strike the "Returns" clause (p5) which adds nothing

Issue - State: closed - Opened by arturl over 10 years ago - 1 comment
Labels: LWG_Cologne

#72 - Apply some comments from LWG's Cologne review.

Pull Request - State: closed - Opened by jyasskin over 10 years ago - 2 comments

#71 - LEWG: no need to describe deferred features

Issue - State: closed - Opened by arturl over 10 years ago

#70 - LEWG: when_any should return when_any_result struct; remove when_any_back

Issue - State: closed - Opened by arturl over 10 years ago - 26 comments

#69 - Policy for futures created through future::then in case of implicit unwrapping

Issue - State: closed - Opened by Matthias247 almost 11 years ago - 1 comment

#68 - should make_ready_future take in account std::ref parameters?

Issue - State: closed - Opened by viboes almost 11 years ago - 4 comments

#67 - Unwrapping constructors on future and shared_future

Issue - State: closed - Opened by arturl almost 11 years ago
Labels: enhancement

#66 - Missing angle brackets in 3.4

Issue - State: closed - Opened by arturl almost 11 years ago
Labels: Urbana

#65 - minor indentation issues.

Pull Request - State: closed - Opened by viboes almost 11 years ago - 1 comment

#64 - variadic when_any_back

Issue - State: closed - Opened by K-ballo almost 11 years ago - 5 comments

#63 - Address #55: shared_future<R>::then should be const

Pull Request - State: closed - Opened by K-ballo almost 11 years ago - 1 comment

#62 - Replace typename in template arguments with class

Pull Request - State: closed - Opened by K-ballo almost 11 years ago - 1 comment

#61 - Address #56 shared_future::then continuation should take a shared_future not a future.

Pull Request - State: closed - Opened by viboes almost 11 years ago - 1 comment

#60 - Addressing issue #59 - Add make_exceptional_future.

Pull Request - State: closed - Opened by viboes almost 11 years ago

#59 - Add make_exceptional_future

Issue - State: closed - Opened by viboes almost 11 years ago - 1 comment
Labels: enhancement, Fixed_in_N4123

#58 - Unwrapping shared_future

Issue - State: closed - Opened by hkaiser almost 11 years ago - 6 comments
Labels: enhancement, Fixed_in_N4123

#57 - Address #51: when_all/when_any result type

Pull Request - State: closed - Opened by K-ballo almost 11 years ago - 6 comments

#56 - shared_future::then continuation should take a shared_future not a future.

Issue - State: closed - Opened by viboes almost 11 years ago - 7 comments
Labels: Fixed_in_N4123

#55 - shared_future<R>::then should be const

Issue - State: closed - Opened by K-ballo almost 11 years ago - 4 comments
Labels: Fixed_in_N4123

#54 - future unwrapping constructor wording

Issue - State: closed - Opened by viboes almost 11 years ago
Labels: Fixed_in_N4123

#53 - Drop all "`R` may be `void`" notes

Issue - State: closed - Opened by K-ballo almost 11 years ago - 1 comment
Labels: Fixed_in_N4123

#52 - when_all/when_any post condition

Issue - State: closed - Opened by viboes almost 11 years ago
Labels: Fixed_in_N4123

#51 - when_all/when_any result type.

Issue - State: closed - Opened by viboes almost 11 years ago - 9 comments
Labels: Fixed_in_N4123

#50 - Take care of #46, #47, #48

Pull Request - State: closed - Opened by viboes almost 11 years ago - 1 comment

#49 - future::then() requires F is callable with a future<R>

Issue - State: closed - Opened by viboes almost 11 years ago - 1 comment
Labels: Fixed_in_N4123

#48 - Missing std::experimental::async

Issue - State: closed - Opened by viboes almost 11 years ago - 11 comments
Labels: Fixed_in_N4123

#47 - Add the synopsis section for <experimental/future> file

Issue - State: closed - Opened by viboes almost 11 years ago
Labels: Fixed_in_N4123

#46 - Adapt Namespaces, headers from Fundamentals TS

Issue - State: closed - Opened by viboes almost 11 years ago - 2 comments
Labels: Fixed_in_N4123

#45 - The text for when_any_back is messed up, refers to when_all

Issue - State: closed - Opened by arturl almost 11 years ago - 1 comment
Labels: Fixed_in_N4123

#44 - Revisit 'Effects' for when_all/when_any/when_any_back to allow for shared_future

Issue - State: closed - Opened by arturl almost 11 years ago - 1 comment
Labels: Fixed_in_N4123

#43 - §2.2 6 Could the result future of ::then() block on the destructor as the one of async?

Issue - State: closed - Opened by viboes almost 11 years ago - 10 comments
Labels: Fixed_in_N4123

#42 - Why the variadic versions of when_all/when_any could return a future vector?

Issue - State: closed - Opened by viboes almost 11 years ago - 2 comments

#41 - When the result of when_all/when_any becomes ready?

Issue - State: closed - Opened by viboes almost 11 years ago - 5 comments
Labels: Fixed_in_N4123

#40 - §2.4 2 Missing <class InputIterator>

Issue - State: closed - Opened by viboes almost 11 years ago - 1 comment
Labels: Fixed_in_N4123

#39 - §2.4 7 replace output by input.

Issue - State: closed - Opened by viboes almost 11 years ago - 1 comment
Labels: Fixed_in_N4123

#38 - §2.4 4 replace when_any by when_all

Issue - State: closed - Opened by viboes almost 11 years ago
Labels: Fixed_in_N4123

#37 - Need to specify behavior of when_any and when_all with deferred tasks

Issue - State: closed - Opened by arturl almost 11 years ago - 2 comments
Labels: Fixed_in_N4123

#36 - Specify validity of implicitly unwrapped future

Issue - State: closed - Opened by arturl almost 11 years ago - 2 comments
Labels: Fixed_in_N4123

#35 - missing unwrap

Issue - State: closed - Opened by viboes about 11 years ago - 1 comment

#34 - when_ missing precondition

Issue - State: closed - Opened by viboes about 11 years ago - 15 comments
Labels: Fixed_in_N4123

#33 - Replace thrid by second

Issue - State: closed - Opened by viboes about 11 years ago

#32 - Remove scheduler word

Issue - State: closed - Opened by viboes about 11 years ago

#31 - typo "The three functions "

Issue - State: closed - Opened by viboes about 11 years ago

#30 - Clarifications to .then() Effects clause

Issue - State: closed - Opened by viboes about 11 years ago - 1 comment

#29 - clarifications on when_all() effects second

Issue - State: closed - Opened by viboes about 11 years ago
Labels: Fixed_in_N4123

#28 - clarifications on when_all() effects

Issue - State: closed - Opened by viboes about 11 years ago - 2 comments
Labels: Fixed_in_N4123

#27 - Add a postcondition to .then()

Issue - State: closed - Opened by viboes about 11 years ago
Labels: Fixed_in_N4123

#26 - Clarification on .then() postconditions

Issue - State: closed - Opened by viboes about 11 years ago - 4 comments
Labels: Fixed_in_N4123

#25 - valid() clarifications

Issue - State: closed - Opened by viboes about 11 years ago - 4 comments
Labels: Fixed_in_N4123

#24 - is_ready clarifications

Issue - State: closed - Opened by viboes about 11 years ago - 7 comments
Labels: Fixed_in_N4123

#23 - Missing description of what is returned by .then()

Issue - State: closed - Opened by viboes about 11 years ago
Labels: Fixed_in_N4123

#22 - Typo in 3.2 Changes to class template future §10

Issue - State: closed - Opened by viboes about 11 years ago - 1 comment
Labels: Fixed_in_N4123

#21 - Type in 3.2 Changes to class template future §9

Issue - State: closed - Opened by viboes about 11 years ago
Labels: Fixed_in_N4123

#20 - should we use system_clock or steady_clock in add_after method?

Issue - State: closed - Opened by arturl about 11 years ago - 3 comments

#19 - Remove Require clause in serial_executor::serial_executor

Issue - State: closed - Opened by viboes about 11 years ago

#18 - Unclear description for 2.6.4 §2

Issue - State: closed - Opened by viboes about 11 years ago - 1 comment

#16 - Typo in 2.6.2 §4

Issue - State: closed - Opened by viboes about 11 years ago

#15 - Add a Throw clause for executor::add

Issue - State: closed - Opened by viboes about 11 years ago

#14 - Transform Notes on Require clause fro ~executor()

Issue - State: closed - Opened by viboes about 11 years ago - 3 comments

#13 - Remove subjetive sentences as "but in general such use is risky"

Issue - State: closed - Opened by viboes about 11 years ago - 1 comment

#12 - Replace function<void> by a specific class work/job

Issue - State: closed - Opened by viboes about 11 years ago - 4 comments

#11 - Maybe, make clearer that closure are executed completly on the same thread

Issue - State: closed - Opened by viboes about 11 years ago - 1 comment

#10 - New files should be included as <experimental/xxxx>

Issue - State: closed - Opened by viboes about 11 years ago

#9 - Shouldn't this TS inline the concurrency_v1 namespapce for the new classes/functions?

Issue - State: closed - Opened by viboes about 11 years ago - 1 comment

#7 - Typo in std::function

Issue - State: closed - Opened by arturl about 11 years ago

#6 - Revisit the use of <cxx-notes>

Issue - State: closed - Opened by arturl over 11 years ago - 1 comment

#5 - Find a better name for when_any_swapped, allow reorder

Issue - State: closed - Opened by arturl over 11 years ago - 1 comment

#4 - Function ready() must be spelled is_ready()

Issue - State: closed - Opened by arturl over 11 years ago - 1 comment

#3 - Need better name for thread_executor

Issue - State: closed - Opened by arturl over 11 years ago

#1 - Fixed formatting of serial_executor batching note

Pull Request - State: closed - Opened by austern over 11 years ago - 2 comments