Memory Corruption with clang-cl about args HOT 2 CLOSED

I can't replicate the issue. Based on the incorrect output you are reporting, that would be having issue in the int main loop that prints, completely separate from your use of args. This would point to an issue in clang-cl on Windows, and not this library. Really, everything you output doesn't touch this library at all, so I don't think this issue tracker is the correct place for this issue. I thought it might be this library touching something that it shouldn't, but you are constructing your _args and args vector immediately before the problem output; I don't see how this library could be responsible for this.
I'd recommend either asking in the appropriate issue tracker, or possibly going to a more general-purpose C++ help channel, like ##c++-general on irc.freenode.net or something.

from args.

Thanks for looking into it. I agree it is probably a problem in clang-cl. For reference, I managed to simplify the sample to 40 lines, and without args :

#include <iostream>
#include <unordered_set>
#include <vector>

struct EitherFlag
{
	static auto GetLong(std::initializer_list<char>)
	{
		return std::unordered_set<std::string>{ "" };
	}
};

auto other_main()
{
	EitherFlag::GetLong({});
	try
	{
		throw 1;
	}
	catch (...)
	{
	}
}

int main(int argc, char* argv[])
{
	for (auto i = 0; i < 2; ++i)
	{
		auto args = std::vector<std::string>{ "a", "b" };
		if (args.at(1) != "b")
		{
			std::cerr << "Bug detected! (at i = " << i << ")" << std::endl;
			return 1;
		}
		other_main();
	}
	std::cerr << "Everything went fine :)" << std::endl;
	return 0;
}

which prints

Bug detected! (at i = 1)

I also opened a ticket on LLVM bugtracker:
https://bugs.llvm.org/show_bug.cgi?id=43900

from args.