@microsoft-github-policy-service agree

I'll take a look at this tomorrow in the debugger. I got COVID, whee

taking a look tomorrow (12-01)

Huh, error_condtion?

I was using the test template that was suggested in the other PR so I wound up using this:

#include <future>
#include <ios>
#include <string>
#include <system_error>

struct my_error_category : public std::error_category {
	const char* name() const noexcept override {
		return "potato";
	}

	std::string message(int) const override {
		return "message goes here";
	}
};

int main() {
	auto& generic_cat = std::generic_category();
	auto& system_cat = std::system_category();
	auto& iostream_cat = std::iostream_category();
	auto& future_cat = std::future_category();
	const auto& my_cat = my_error_category();

	std::error_code generic(42, generic_cat);
	std::error_code system(42, system_cat);
	std::error_code iostream(42, iostream_cat);
	std::error_code future(42, future_cat);
	std::error_code my(42, my_cat);
}

On my install of VS, this winds up looking like this:

Enabling functions calls in value formatting winds up looking like this:

So I don't think I'm replicating what you're seeing. Would you mind sharing your code/some screenshots so I have a better idea of what's going on?

I misunderstood! I misread error_category as error_condition somehow; this does seem reasonable to me, then, although I don't know how comfortable people generally are with function calls in visualizers...

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

Thanks for implementing these visualizers, and congratulations on your first microsoft/STL commit! 🎉 😻 🚀

We've merged this to the GitHub and MSVC-internal repos, but we still need to "triple-mirror" our accumulated visualizer changes to the VS repo so they will actually take effect in the IDE. I believe that @CaseyCarter will be looking into doing that soon.