use assertions for this. If your code is a container that returns a size, be sure to use a type that will accommodate any possible usage of your container. When in doubt, use a larger type rather than calls to new commonly falls into this category, as does use of auto in a range-based loop over a container whose type is spelled out nearby. • (Allowed) When the type doesn’t matter because it isn’t being from boost/multi_index • Heap from boost/heap • The flat containers from Container: boost/container/flat_map, and boost/container/flat_set • Intrusive from boost/intrusive. We are actively considering

and operators for types that support them, like lists, dic- tionaries, and files. Definition: Container types, like dictionaries and lists, define default iterators and membership test operators (“in” too. 7 Prefer these methods to methods that return lists, except that you should not mutate a container while iterating over it. Yes: for key in adict: ... if key not in adict: ... if obj in alist:

Target Link CK ML Systems http://ctuning.org CWL Analysis Workflows http://commonwl.org Popper Container Workflows https://github.com/ systemslab/popper ReproZip General-purpose Bundles http://reprozip