Name | Date | Size | #Lines | LOC | ||
---|---|---|---|---|---|---|
.. | - | - | ||||
DEPS | D | 03-May-2024 | 80 | 4 | 3 | |
README.md | D | 03-May-2024 | 1.1 KiB | 28 | 19 | |
bind.h | D | 03-May-2024 | 18.6 KiB | 482 | 158 | |
bind_internal.h | D | 03-May-2024 | 71.3 KiB | 1,859 | 1,157 | |
bind_unittest.cc | D | 03-May-2024 | 66.6 KiB | 2,107 | 1,557 | |
bind_unittest.nc | D | 03-May-2024 | 24 KiB | 596 | 460 | |
callback.h | D | 03-May-2024 | 18.9 KiB | 497 | 274 | |
callback_forward.h | D | 03-May-2024 | 687 | 25 | 11 | |
callback_helpers.cc | D | 03-May-2024 | 1,019 | 44 | 29 | |
callback_helpers.h | D | 03-May-2024 | 7.9 KiB | 226 | 122 | |
callback_helpers_unittest.cc | D | 03-May-2024 | 10 KiB | 301 | 232 | |
callback_internal.cc | D | 03-May-2024 | 1.9 KiB | 73 | 52 | |
callback_internal.h | D | 03-May-2024 | 7.8 KiB | 220 | 130 | |
callback_tags.h | D | 03-May-2024 | 922 | 35 | 19 | |
callback_unittest.cc | D | 03-May-2024 | 26.8 KiB | 782 | 651 | |
callback_unittest.nc | D | 03-May-2024 | 5.8 KiB | 145 | 113 | |
disallow_unretained.h | D | 03-May-2024 | 2.9 KiB | 72 | 10 | |
function_ref.h | D | 03-May-2024 | 4 KiB | 107 | 39 | |
function_ref_unittest.cc | D | 03-May-2024 | 2.1 KiB | 91 | 65 | |
function_ref_unittest.nc | D | 03-May-2024 | 2.3 KiB | 57 | 41 | |
identity.h | D | 03-May-2024 | 645 | 29 | 13 | |
identity_unittest.cc | D | 03-May-2024 | 470 | 24 | 12 | |
invoke.h | D | 03-May-2024 | 5.1 KiB | 153 | 84 | |
invoke_unittest.cc | D | 03-May-2024 | 959 | 35 | 19 | |
not_fn.h | D | 03-May-2024 | 1.4 KiB | 57 | 34 | |
not_fn_unittest.cc | D | 03-May-2024 | 680 | 24 | 13 | |
overloaded.h | D | 03-May-2024 | 1.5 KiB | 52 | 11 | |
overloaded_unittest.cc | D | 03-May-2024 | 727 | 28 | 16 | |
overloaded_unittest.nc | D | 03-May-2024 | 760 | 25 | 17 | |
unretained_traits.h | D | 03-May-2024 | 5.5 KiB | 158 | 107 |
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