[llvm-bugs] [Bug 100240] Confirm 'LWG2697 [concurr.ts] Behavior of `future`/`shared_future` unwrapping constructor when given an invalid future' should be marked as 'Nothing to do' in the status page

LLVM Bugs via llvm-bugs llvm-bugs at lists.llvm.org
Tue Jul 23 15:10:44 PDT 2024

Previous message: [llvm-bugs] [Bug 100239] Apply 'LWG2412 `promise::set_value()` and `promise::get_future()` should not race'
Next message: [llvm-bugs] [Bug 100242] Apply 'LWG2995 basic_stringbuf default constructor forbids it from using SSO capacity'
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20240723/4a62ce71/attachment.html>

Previous message: [llvm-bugs] [Bug 100239] Apply 'LWG2412 `promise::set_value()` and `promise::get_future()` should not race'
Next message: [llvm-bugs] [Bug 100242] Apply 'LWG2995 basic_stringbuf default constructor forbids it from using SSO capacity'
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the llvm-bugs mailing list