Stephan T. Lavavej comments

Results 357 comments of


                                            Stephan T. Lavavej

vectorize `min/max_element` using SSE4.1 for floats

I'm *speculatively* mirroring this to the MSVC-internal repo - please notify me if any further changes are pushed.

vectorize `min/max_element` using SSE4.1 for floats

Thanks for maximizing the performance and minimizing the time taken for these algorithms with everyone's favorite types! :rocket: :heart_eyes_cat: :gift:

P0543R3 Saturation Arithmetic

MSVC compiler intrinsics are expected to be available by the time we implement this: ``` _sat_add_i8 _sat_add_i16 _sat_add_i32 _sat_add_i64 _sat_add_u8 _sat_add_u16 _sat_add_u32 _sat_add_u64 _sat_sub_i8 _sat_sub_i16 _sat_sub_i32 _sat_sub_i64 _sat_sub_u8 _sat_sub_u16 _sat_sub_u32...

<atomic>: In pre-C++20 mode, the constructor should be trivial

Is this purely a pair of compiler bugs with no STL changes required? If so, should we close this as `external` `resolved`? (In any event, thanks for the report!)

<atomic>: In pre-C++20 mode, the constructor should be trivial

The purpose of Standard modes is to give customers time to adapt to source-breaking changes. While I don't think it's a *great* idea to provide default-initializing trivial constructors in C++14/17...

`<regex>`: Constants in `std::regex_constants` are not `constexpr` variables

We talked about this at the weekly maintainer meeting and we're basically in agreement that this is legitimately a conformance issue, albeit one of extremely limited importance, and we would...

`flat_set`'s transparent insertion requirements are deficient

We talked about this at the weekly maintainer meeting, although we didn't have time to track down all of the Standardese. (The main question in our minds is whether this...

<filesystem>: create_directory vs create_directories return codes

I've updated your comment to display the trailing backslash (by using backticks for code font).

<filesystem>: create_directory vs create_directories return codes

Also reported as DevCom-10490142.

<filesystem>: prevent filesystem::path dangerous conversions to/from default code page encoding

How exactly does Boost.Filesystem prevent such conversions? According to my understanding, it behaves the same as `std::filesystem` with respect to `char` (although it predated `char8_t`). For an error, this is...