std-discussion

Monday, 27 March 2023

• std::usize()? Marc Mutz

Saturday, 25 March 2023

• Re: std::hash Bjorn Reese
• Re: std::hash Nate Eldredge

Friday, 24 March 2023

• Re: std::hash Marcin Jaczewski
• Re: std::hash Chris Ryan
• std::hash Marcin Jaczewski

Tuesday, 21 March 2023

• Re: C++17 accidentally made pointer arithmetic on type-punned pointers well-defined Christopher Hallock
• Re: C++17 accidentally made pointer arithmetic on type-punned pointers well-defined language.lawyer_at
• C++17 accidentally made pointer arithmetic on type-punned pointers well-defined Christopher Hallock

Thursday, 16 March 2023

• Re: Value of non-active data member byte in constexpr union? language.lawyer_at
• Re: Value of non-active data member byte in constexpr union? language.lawyer_at
• Re: Value of non-active data member byte in constexpr union? Shafik Yaghmour
• Value of non-active data member byte in constexpr union? Stephan Bergmann

Tuesday, 14 March 2023

• Re: [cfenv] Question about C++'s std::fexcept_t vs C's fexcept_t Sam Elliott

Monday, 13 March 2023

• Re: [cfenv] Question about C++'s std::fexcept_t vs C's fexcept_t Jens Maurer
• [cfenv] Question about C++'s std::fexcept_t vs C's fexcept_t Sam Elliott

Tuesday, 7 March 2023

• Re: Data races Marcin Jaczewski
• Re: Data races Vladimir Grigoriev

Monday, 6 March 2023

• Re: Data races Jason McKesson
• Data races Vladimir Grigoriev

Wednesday, 1 March 2023

• Re: possible bit-field prvalue inconsistency Brian Bi
• Re: possible bit-field prvalue inconsistency Daniel Jennings
• Re: possible bit-field prvalue inconsistency Shafik Yaghmour
• Re: possible bit-field prvalue inconsistency Edward Catmur
• possible bit-field prvalue inconsistency Daniel Jennings
• Re: Contradiction in the description of the function std::call_once Giuseppe D'Angelo
• Contradiction in the description of the function std::call_once Vladimir Grigoriev

Last message date: 2023-03-27 09:35:59