As I myself am very curious about answers to your first question unfortunately I am not able to give you any good advice here. To at least give you an answer to your second question: This is the somewhat semi-automatic way I use to manually add missing or adjust changed declarations in out of sync … Read more
Update: The situation got a bit more complicated after the resolution of CWG DR 1684 removed the requirement quoted below. Some more information can be found in this discussion on the std-discussion mailing list and in the related question Why isn’t `std::initializer_list` defined as a literal type? [decl.constexpr]/8: A constexpr specifier for a non-static member … Read more
A polymorphic_allocator is intended to let you have an allocator whose behavior is dynamically determined at runtime. The only way to create a polymorphic_allocator is: Default constructed, in which case it uses std::pmr::get_default_resource() return value, which is a memory_resource*. Pass it a memory_resource*. copy from another polymorphic_allocator. So the point of customization for a polymorphic_allocator … Read more
In previous version of Google Mock you can only mock virtual functions, see the documentation in the project’s page. More recent versions allowed to mock non-virtual methods, using what they call hi-perf dependency injection. As user @congusbongus states in the comment below this answer: Google Mock relies on adding member variables to support method mocking, … Read more
Have you also looked at its memory consumption? Note that quicksort itself is worse than linear, with a quite bad worse case runtime. This multiplies with the worse than linear runtime behaviour of certain steps of template compilation and instantiation (sometimes those are exponentional). You should maybe graph your compiletime for various datasets to observe … Read more
There’s a proposal on the issue titled Forward declarations of nested classes P0289R0. However as you can see from the last Trip Report: C++ Standards Meeting in Jacksonville, February 2016, this proposal was pendent to proposals for which further work is encouraged. I’m quoting the verdict of the committee (Emphasis Mine): This would allow things … Read more
I believe libc++ doesn’t support all exception functions yet. See the status page: http://libcxxabi.llvm.org/spec.html You could probably link against gnu’s libstdc++
This code has 3 holes: First hole: int numEntries. Later you do: ++numEntries; You increment unspecified value. Not sure if it’s UB, but still bad. Second and third hole: const int length = numEntries; int* arr = new int[length]; And const int size = numEntries; int matrix[size]; numEntries has unspecified value (first hole). You use … Read more
It’s impossible to do this with CMake. CMake only keeps one set of compiler properties which is shared by all targets in a CMakeLists.txt file. If you want to use two compilers, you need to run CMake twice. This is even true for e.g. building 32bit and 64bit binaries from the same compiler toolchain. The … Read more
To me it sounds like someone messed up merging the previous standard with the new one. Previously the standard said this: (C++14 N4140, 7.1.6.4.7 [dcl.spec.auto]): When a […] return statement occurs in a function declared with a return type that contains a placeholder type, the deduced return type or variable type is determined from the … Read more