remove_if is already stable, so separate stable and unstable versions are unnecessary.
https://iterator.wordpress.com/2016/01/31/algorithms_0/
Unstable remove_if algorithms are possible that might win, as indicated in that article; but plain remove_if provides the most consistent behavior.
The current names and titles of the examples put too much emphasis on the package which is being demonstrated rather than the concept. This can be jarring for newcomers. This patch renames them to put the emphasis on the concept instead.
* [Vulkan] Add a vulkan port based on the cuda port
* Add VULKAN_SDK env variable to whitelist
* * Added some additional diagnostic information
* Corrected if NOT exists statement
* New package: cutelyst2
A C++ Web Framework built on top of Qt, using the simple approach of Catalyst (Perl) framework.
* [cutelyst2] Rearrange files; prefer ninja.
* Update google-cloud-cpp to 0.3.0.
A new release of google-cloud-cpp, with some improvements in packaging
that simplified the port files.
* [google-cloud-cpp] Fix OSX builds
* make user wide integration not burn everything if LLVM is used as a toolset.
(e.g. cmake -G "VS" -TLLVM fails to even find compiler due to linker issues)
fixes#4359 but might have side effects for that toolset.
(e.g. not automatically adding dependencies)
* remove whitespaces
* [vcpkg-integrate] Conform to MSBuild conventions for comparisons
* [bzip2] Fix tools install directory
Change to install tools in port name directory. (vcpkg/installed/<triplet>/tools/bzip2)
* [bzip2] Modernize and bump control version
* [portaudio] Enable debug output.
This is enabled by default in the original MSVC project in the PortAudio
distribution, but not in their CMake build. This commit fixes the
regression.
I don't think there are any performance concerns with this, as PortAudio
(AFAICT) does not log from performance-critical code.
Note that this change might still be somewhat controversial, because
PortAudio will by default dump its debug output directly to stderr,
which is not particularly nice. However, the alternative is not having
any way for end users to troubleshoot PortAudio issues at all, which
IMHO is worse. Applications can always call
`PaUtil_SetDebugPrintFunction()` to redirect the output away from
stderr, and I encourage them to do so.
* [portaudio] Bump control version
