Casey Carter

From #4989 😸: > Perfect, thank you! 😻 > > We merge PRs to our GitHub and MSVC-internal repos simultaneously in a semi-manual process, batched up to save time. Your...

> > * In vNext we should completely get rid of `function`. > > I think it worth creating vNext issue. We already have #321. EDIT: ... which will probably...

I suspect vNext on this issue was really "we want to rewrite this entire mess in vNext and that will be 'soon' so let's avoid wasting time on it for...

> I don't know what you would do about it other than suppression. `/fp:fast` is indeed asking for UB for NANs. Ideally, we don't test undefined behavior. It tends to...

I completely agree with your interpretation of the Standard, and believe we should label this "LWG issue needed" instead of "bug". I think it's nonsensical to allow `:#c` with the...

It would be very nice if `RequiresClausePosition` were split into `LeadingRequiresClausePosition` and `TrailingRequiresClausePosition`.

> Removing the LWG label - that's for accepted LWG resolutions that we need to implement. I should have seen the bot messages. "Blocked on LWG" seems appropriate, no?

Works fine for me on my "Beta: Use UTF-8 for language support" machine, and the same for Compiler Explorer (https://www.godbolt.org/z/oGMbo3YE1). The problem is most likely: 1. The compiler and editor...

I'm not sure there's a bug here. If the library is throwing `ERROR_NO_UNICODE_TRANSLATION` to tell you that there are characters in the `path` that can't be represented in the active...

`/utf-8` makes an ENORMOUS difference, we're working on spreading that effect to other encodings. Benchmark code: ```c++ #define _CRT_SECURE_NO_WARNINGS #include #include #include #include #include void std_sprintf(benchmark::State& s) { for (auto...