Viewing profile — pfultz2

Yea and C++ static analysis tools already warn for the case, so even for new C++ programmers where it might not be entirely obvious, its still easy to catch the error.

You dont need annotations, cppcheck already warns with: test.cpp:16:45: error: Using object that is a temporary. [danglingTemporaryLifetime] assert((std::vector {1, 2, 3, 4} == app…

Concepts specify constraints on templates, but the types are still templates, so you can't put the function definition in a .cpp file nor put them into a vector(which is what type …

That seems more like type erasure as defined in Java where the container is the same for all data types and the compiler implicitly inserts casts from the base type to the paramete…

But cppcheck can find a lot of dangling references with lambda captures.

Clang's lifetime profile will catch the first example: :8:16: warning: passing a dangling pointer as argument [-Wlifetime] std::cout :7:38: note: temporary was destroyed at the end…

Meson looks nice, but it still lacks a way to tell it where your dependencies are installed(like cmake’s CMAKE_PREFIX_PATH). You can try to get by, by setting pkg config path, but …

> For the sake of history, `range` was found/coined by Andrei No it wasn't. Boost.Range library predates Andrei's Range talk in 2009. Boost.Range was introduced in boost 1.32, whic…

Higher density may allow for more volume but it can increase viscosity.

Daniel Pfeffier’s effective cmake talks about how to do that. Setup each project standalone and get the dependencies with find_package. Then create a superprojects thats add each d…

> What does that do? It makes the variable x refer to the object that y is referring to In Java/C#, it doesn't always: int x = 1; int y = 2; x = y; The variable `x` does not refer …

> Currently there is no buildsystem that enables users to describe the requirements of an project correctly. We want to steer away from standardizing a build system for now. The us…

The package managers that are listed in the post are cross-platform and work on windows.

Or rather, I would like to hear your opinion instead. Would buckaroo consider using a standard package metadata similar to what I outlined? I believe buckaroo uses integrated build…

> I'm surprised the author forgot to consider platform architectures That is mainly for binary distribution. Most C++ package managers currently are source-based because binary com…

> Wonder if Nix package manager would work here. The problem is extra work is needed to support things like cross compilation. Instead, you want to pass a toolchain file that descr…

You can't do that with United Airlines. The answers have to be picked from a drop-down of answers.

Last time I looked at Nix it had a problem with dealing with cross-compilation. The problem is mainly that many packages still use autotools which does not have a descriptive toolc…

This sound similar to cmake-get: https://github.com/pfultz2/cmake-get

pkg-config works on windows with visual studio as well.

Actually cget can install packages directly from cmake packages(or other build systems). There is also the cmake-get module which can install cget recipes directly in the cmake wit…

The nice things about cget is that even though it uses python(which is mainly for easy distribution), the cget protocol only has a dependency on cmake. So cmake modulues like cmake…

> Too many C++ tools couple package management and build Conan does this too. If I follow the instructions to integrate cmake with conan, I would write something like this: include…

There is cget which install cmake packages out of the box, so many libraries don't need to be updated to support it: https://github.com/pfultz2/cget