std::vector<int> b = a; will this creates b as a copy (new object with same contents) of vector a or as a reference to it? that create b as a new vector being a copy, so b.append(1); does not change a solved Std::vectors – copying vs creating a reference
You need to link to the standard Vector. std::vector solved how to define a vector
The original poster failed to actually post the code that was causing the problem. He has since edited my post with the correct code that demonstrates the problem. The code that demonstrates the problem follows: template <class R, typename B=int> class AVectorContainer { public: AVectorContainer() {} typedef R* ptr_Type; typedef const B & const_ref_Type; typedef … Read more
Dict* test = (Dict*)malloc(sizeof(Dict)); does not do what you think it does. malloc allocates a block of memory, but does not initialize it. So later on, when you call test->nodes.push_back, you’re calling into uninitialized memory. Undefined behavior. In your case, it crashes. The solution here is allocate test with new, which will initialize both test … Read more
Do exactly what the compiler told you to do, enable C++ 11 by passing -std=c++11 as an argument. solved storing values in a custom stuct creates compiler error [c++] [closed]
So how is the 10000th element stored here? The element isn’t stored in the vector. It’s ‘stored’ in a piece of memory that is unrelated to the vector. Isn’t the expected behavior here a “Segmentation fault”? No. The behaviour is undefined, so there is no behaviour to expect. But the above runs successfully. That’s a … Read more
Here are the ones I know of: Traditional a.k.a. plain a.k.a. C array vector unique_ptr with an array-type template argument array valarray dynarray static_vector (see also here) small_vector stable_vector There are also “variable-length arrays” and “arrays with runtime bounds”, which do not exist in C++; the former exists in C. See also this question and … Read more
Indeed push_back may trigger reallocation, which is a slow process. It will not do so on every single push_back though, instead it will reserve exponentially more memory each time, so explicit reserve only makes sense if you have a good approximation of resulting vector size beforehand. In other words, std::vector already takes care of what … Read more
Vectors in c++ are dynamically sized. You can create a vector without a size argument in the constructor then push size number of elements like so: vector<int> makeGaps (int size){ vector<int> vectorOfGaps; for(int i = 0; i < size;i++){ vectorOfGaps.push_back(i); } return vectorOfGaps; } Edit: Also, as someone already pointed out in your comments, it … Read more