Alcaro
Alcaro
The easiest fix is tell people to #define NOMINMAX before including windows.h, or include Dragonbox before windows.h. But that's kinda impolite, so I agree with doing something. `(std::min)(a,b)` works, yes....
libco is not thread safe by default. Define LIBCO_MP in your build; either via some build system flag, or by editing libco.h or settings.h. I'm not a huge fan of...
They're up to compiler 19.44 / VS 17.14 by now https://learn.microsoft.com/en-us/cpp/overview/compiler-versions?view=msvc-170
Isn't that chip the most cpu intensive to emulate of them all? Not much we can do here. Switch to HLE or overclock your CPU.
On the other hand, breaking it with no notice is arguably impolite. And [the releases](https://github.com/brechtsanders/winlibs_mingw/releases/tag/14.1.0posix-18.1.7-12.0.0-ucrt-r2) mention working on Windows 7 (in a roundabout way that actually means the output programs...
I kinda like how make clean keeps the dir, makes things jump around less if a graphical file browser is open in that dir. For the same reason, I'm not...
> However generally speaking a clean target is intended to remove files and directories created during the build process Yeah, opinions on build systems vary as much as opinions on...
Yes, but what is said good reason? That one's fixable by making the makefile itself a dependency. Flips is small; debug builds only take a second, and the optimized one...
Version 2: Also fixes \x00-\xFF matching wrong things (there are few bytes = 0)
Version 3: Also fixes non-range chars in classes, so `[a-zñ]+` will match `piñata`