Name Date Size #Lines LOC

..--

DEPSH A D25-Apr-202580 43

README.mdH A D25-Apr-20251.1 KiB2819

bind.hH A D25-Apr-202516.6 KiB437132

bind_internal.hH A D25-Apr-202578.1 KiB2,0211,253

bind_nocompile.ncH A D25-Apr-202520 KiB364330

bind_unittest.ccH A D25-Apr-202567.1 KiB2,1441,567

callback.hH A D25-Apr-202519.4 KiB519292

callback_forward.hH A D25-Apr-2025687 2511

callback_helpers.ccH A D25-Apr-20251,019 4429

callback_helpers.hH A D25-Apr-202510.4 KiB292164

callback_helpers_unittest.ccH A D25-Apr-202514.9 KiB393316

callback_internal.ccH A D25-Apr-20251.9 KiB6946

callback_internal.hH A D25-Apr-20259.1 KiB266170

callback_nocompile.ncH A D25-Apr-20254 KiB7159

callback_tags.hH A D25-Apr-2025922 3519

callback_unittest.ccH A D25-Apr-202526.9 KiB790652

concurrent_callbacks.hH A D25-Apr-20253.8 KiB12858

concurrent_callbacks_unittest.ccH A D25-Apr-20253.4 KiB13493

concurrent_closures.ccH A D25-Apr-20251.4 KiB5036

concurrent_closures.hH A D25-Apr-20252.3 KiB8228

concurrent_closures_unittest.ccH A D25-Apr-20252.1 KiB9762

disallow_unretained.hH A D25-Apr-20252.9 KiB7210

function_ref.hH A D25-Apr-20255.8 KiB13442

function_ref_nocompile.ncH A D25-Apr-2025979 2216

function_ref_unittest.ccH A D25-Apr-20257.3 KiB221155

overloaded.hH A D25-Apr-20251.5 KiB5211

overloaded_nocompile.ncH A D25-Apr-2025811 2417

overloaded_unittest.ccH A D25-Apr-2025727 2816

unretained_traits.hH A D25-Apr-20255.7 KiB13882

README.md

1# base/functional library
2
3[TOC]
4
5## What goes here
6
7This directory contains function objects from future STL versions and closely
8related types.
9
10Things should be moved here that are generally applicable across the code base.
11Don't add things here just because you need them in one place and think others
12may someday want something similar. You can put specialized function objects in
13your component's directory and we can promote them here later if we feel there
14is broad applicability.
15
16### Design and naming
17
18Fundamental [//base principles](../README.md#design-and-naming) apply, i.e.:
19
20Function objects should either come directly from the STL or adhere as closely
21to STL as possible. Functions and behaviors not present in STL should only be
22added when they are related to the specific function objects.
23
24For STL-like function objects our policy is that they should use STL-like naming
25even when it may conflict with the style guide. So functions and class names
26should be lower case with underscores. Non-STL-like classes and functions should
27use Google naming. Be sure to use the base namespace.
28