containers

Besides the fact that the standard defines it to be contiguous, why is std::vector contiguous? If it runs out of space, it needs to reallocate a new block and copy the old block to the new one before continuing. What if it wasn't contiguous? When the storage fills up, it would just allocate a new block and keep the old block. When accessing through an iterator, it would do simple >, < checks to see which block the index is in and return it. This way it doesnt need to copy the array every time it runs out of space. Would this really work/be better? or am i missing something? If std::vector didn

Several articles have been extremely helpful in understanding Docker's volume and data management. These two in particular are excellent: http://container-solutions.com/understanding-volumes-docker/ http://www.alexecollins.com/docker-persistence/ However, I am not sure if what I am looking for is discussed. Here is my understanding: When running docker run -v /host/something:/container/something the host files will overlay (but not overwrite) the container files at the specified location. The container will no longer have access to the location's previous files, but instead only have access to

How do I copy or move the first n elements of a std::vector<T> into a C++11 std::array<T, n> ? Use std::copy_n std::array<T, N> arr; std::copy_n(vec.begin(), N, arr.begin()); Edit: I didn't notice that you'd asked about moving the elements as well. To move, wrap the source iterator in std::move_iterator . std::copy_n(std::make_move_iterator(v.begin()), N, arr.begin()); You can use std::copy : int n = 2; std::vector<int> x {1, 2, 3}; std::array<int, 2> y; std::copy(x.begin(), x.begin() + n, y.begin()); And here 's the live example. If you want to move, instead, you can use std::move : int n = 2

I'm trying to save a couple of files to a container file. The files can be modified later which means the container might have to be enlarged. The user should only see this container as a single file in the file system. The application is written in C++ and running on Windows, but the files should be portable to other platforms as well. The requirements for the container format are: 1. Size : Allow files bigger than 4GB. 2. Portability : It should be feasible to open the container files on other platforms. 3. Performance : When changing a file inside the container, only the "chunks" that

I have a Docker container that performs a single large computation. This computation requires lots of memory and takes about 12 hours to run. I can create a Google Compute Engine VM of the appropriate size and use the "Deploy a container image to this VM instance" option to run this job perfectly. However once the job is finished the container quits but the VM is still running (and charging). How can I make the VM exit/stop/delete when the container exits? When the VM is in its zombie mode only the stackdriver containers are left running: $ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS