__gnu_pbds::hash_exponential_size_policy(3) centos man page | unix.com

Man Page: __gnu_pbds::hash_exponential_size_policy

Operating Environment: centos

Section: 3

__gnu_pbds::hash_exponential_size_policy< Size_Type >(3)     Library Functions Manual	  __gnu_pbds::hash_exponential_size_policy< Size_Type >(3)

NAME
__gnu_pbds::hash_exponential_size_policy< Size_Type > -
SYNOPSIS
Public Types typedef Size_Type size_type Public Member Functions hash_exponential_size_policy (size_type start_size=8, size_type grow_factor=2) void swap (hash_exponential_size_policy< Size_Type > &other) Protected Member Functions size_type get_nearest_larger_size (size_type size) const size_type get_nearest_smaller_size (size_type size) const Detailed Description template<typename Size_Type = std::size_t>class __gnu_pbds::hash_exponential_size_policy< Size_Type > A size policy whose sequence of sizes form an exponential sequence (typically powers of 2. Definition at line 413 of file hash_policy.hpp. Constructor &; Destructor Documentation template<typename Size_Type > __gnu_pbds::hash_exponential_size_policy< Size_Type >::hash_exponential_size_policy (size_typestart_size = 8, size_typegrow_factor = 2) Default constructor, or onstructor taking a start_size, or constructor taking a start size and grow_factor. The policy will use the sequence of sizes start_size, start_size* grow_factor, start_size* grow_factor^2, ... Definition at line 44 of file hash_policy.hpp. Author Generated automatically by Doxygen for libstdc++ from the source code. libstdc++ Tue Jun 10 2014 __gnu_pbds::hash_exponential_size_policy< Size_Type >(3)
Related Man Pages
__gnu_pbds::sample_ranged_hash_fn(3) - centos
__gnu_pbds::sample_range_hashing(3) - centos
__gnu_pbds::sample_range_hashing(3cxx) - debian
__gnu_pbds::sample_ranged_hash_fn(3cxx) - debian
__gnu_pbds::sample_size_policy(3cxx) - debian
Similar Topics in the Unix Linux Community
Set hard block limit for user using quota
Best performance UNIX just for HOST Virtualization?
CentOS7 restoring file capabilities
Unsure why access time on a directory change isn't changing
Controlling user input