containers

As a result of this question from a few days ago there are a few things that have been bugging me about the complexity requirements for std::deque::push_back/push_front vs the actual std::deque implementations out in the wild. The upshot of the previous question was that these operations are required to have O(1) worst case complexity. I verified that this was indeed the case in c++11 : from 23.3.3.4 deque modifiers, refering to insert, push/emplace front/back Complexity: The complexity is linear in the number of elements inserted plus the lesser of the distances to the beginning and end of

Are there any C++ transformations which are similar to itertools.groupby() ? Of course I could easily write my own, but I'd prefer to leverage the idiomatic behavior or compose one from the features provided by the STL or boost . #include <cstdlib> #include <map> #include <algorithm> #include <string> #include <vector> struct foo { int x; std::string y; float z; }; bool lt_by_x(const foo &a, const foo &b) { return a.x < b.x; } void list_by_x(const std::vector<foo> &foos, std::map<int, std::vector<foo> > &foos_by_x) { /* ideas..? */ } int main(int argc, const char *argv[]) { std::vector<foo>

After another question about iterators I'm having some doubts about custom containers. In my container, iterator is a subclass of const_iterator , so that I get conversion from non-const to const "for free". But is this allowed or are there any drawbacks or non-working scenarios for such a setup? Yes, this is fine. This is how VC10's implementation of the iterators for vector are structured, for example. See _Vector_iterator and _Vector_const_iterator in <vector> . By the way, writing iterators is hard. It's worth your time to learn and use the boost::iterator library. Subclassing seems

I'm getting started with docker by reading some blogs and introduction material. My understanding is docker can wrap a single application into a standardized container. The container provides a sandbox, all the necessary resources the application needs to run, and the application inside always live within that container. That means I can ship the container to everywhere( different kind of OS or even cloud platforms ) and it should still can be run correctly. If my understanding is correct, then does that mean maybe microsoft can wrap their office suits into a container and I can install and

All the demo I saw lately are oriented Asp.net core (I am not sure how it's stable and functional, as it didn't contain all asp.net features), as Windows server 2016 support containers (and docker), should we be able to deploy an asp.net mvc 4.0 app ? Yes. You can use microsoft/windowsservercore or microsoft/iis as a base image, install full ASP.NET and run your 'legacy' .NET apps in containers on Windows. You can do it now with Windows 10 and Server 2016 TP5, but the RTM (expected next week at Ignite) should be more stable. I've shown this by Dockerizing the old Nerd Dinner showcase app . You

I need to store a series of data-points in the form of (name, value), where the value could take different types. I am trying to use a class template for each data-point. Then for each data-point I see, I want to create a new object and push it back into a vector. For each new type, I need to create a new class from the template first. But I can not store the objects created in any vector, since vectors expect the same type for all entries. The types I need to store can not be fitted in a inheritance hierarchy. They are unrelated. Also there can be more types created in future, and I do not