boost/container

mirror of https://github.com/boostorg/container.git synced 2026-02-23 03:32:14 +00:00

Go to file

Ion Gaztañaga 958fe7d326 Fixes #330 : ("boost/container/detail/pair.hpp: partial specializations of boost::move_detail traits for std::pair break Unity (jumbo)")

2026-02-16 22:53:37 +01:00

add drone config [ci skip]

2021-01-21 19:30:35 +00:00

.github/workflows

Rollback to default cygwin mirro

2026-02-04 00:04:27 +01:00

Rename segmented_vector to segtor, to reserve "vector" name to contiguous memory containers.

2026-02-07 15:04:21 +01:00

Move inter-lib dependencies to a project variable and into the build targets.

2024-07-23 22:34:23 -05:00

Fixes #330 : ("boost/container/detail/pair.hpp: partial specializations of boost::move_detail traits for std::pair break Unity (jumbo)")

2026-02-16 22:53:37 +01:00

Rename segmented_vector to segtor, to reserve "vector" name to contiguous memory containers.

2026-02-07 15:04:21 +01:00

include/boost/container

Fixes #330 : ("boost/container/detail/pair.hpp: partial specializations of boost::move_detail traits for std::pair break Unity (jumbo)")

2026-02-16 22:53:37 +01:00

[skip ci] Add "cxxstd" json field. The "cxxstd" json field is being added to each Boost library's meta json information for libraries in order to specify the minumum C++ standard compilation level. The value of this field matches one of the values for 'cxxstd' in Boost.Build. The purpose of doing this is to provide information for the Boost website documentation for each library which will specify the minimum C++ standard compilation that an end-user must employ in order to use the particular library. This will aid end-users who want to know if they can successfully use a Boost library based on their C++ compiler's compilation level, without having to search the library's documentation to find this out.

2021-01-19 12:39:23 -05:00

Make boost_cont_allocation_command compile under non C99 compilers (e.g. MSVC 2010)

2026-01-24 11:06:04 +01:00

Added, for testing and comparison and benchmarking purposes, experimental "nest" container under "experimental" folder, a C++03 backport and adaptation to use Boost.Container internals of Joaquín López Muñoz's "hub" container proposal (https://lists.boost.org/archives/list/boost@lists.boost.org/thread/6YXMHMARNAEFTGBTZYYAETCAYCYHHKQP/).

2026-02-11 12:05:12 +01:00

.drone.star

add drone config [ci skip]

2021-01-21 19:30:35 +00:00

.gitattributes

Move top-level boost directory over to "devel" (temporarily)

2007-07-31 20:32:15 +00:00

.gitignore

Remove old test/bench files

2025-09-20 09:49:21 +02:00

build.jam

Add bench tests to the regression tests

2026-01-18 16:15:19 +01:00

CMakeLists.txt

Add option to use header-only Boost::container

2025-08-25 23:22:57 +08:00

index.html

Removed trailing whitespaces

2014-05-28 15:50:13 +02:00

LICENSE_1_0.txt

Add Boost Software License

2021-11-18 11:40:54 -05:00

README.md

Update README with active tests

2025-11-25 22:28:08 +01:00

README.md

Boost.Container

Boost.Container, part of collection of the Boost C++ Libraries, implements several well-known containers, including STL containers. The aim of the library is to offer advanced features not present in standard containers, to offer the latest standard draft features for compilers that don't comply with the latest C++ standard and to offer useful non-STL containers.

License

Distributed under the Boost Software License, Version 1.0.

Properties

C++03
Mostly header-only, library compilation is required for few features.
Supports compiler modes without exceptions support (e.g. -fno-exceptions).

Build Status

Branch	Deps	Docs	Tests
`master`
`develop`

Directories

Name	Purpose
`doc`	documentation
`example`	examples
`include`	headers
`proj`	ide projects
`test`	unit tests

More information

Ask questions
Report bugs: Be sure to mention Boost version, platform and compiler you're using. A small compilable code sample to reproduce the problem is always good as well.
Submit your patches as pull requests against develop branch. Note that by submitting patches you agree to license your modifications under the Boost Software License, Version 1.0.
Discussions about the library are held on the Boost developers mailing list. Be sure to read the discussion policy before posting and add the [container] tag at the beginning of the subject line.