You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We already have multiple variants of set_headers() and add_headers() implemented. However - those templated variants which take containers or container pairs assume the element type is a constant C-style string of constant characters (const char* const). What if the user has vectors of std::strings? It's a legitimate scenario... let' cater to it.
The text was updated successfully, but these errors were encountered:
* Added ability to add a single named header
* Reduced the number of `add_headers()` and `set_headers()` function variants, so that the user calls a templated version and the type is determined autogneioammtl
* Moved some add_headers() calls into a proptecte name=
* Added ability to add a single named header to a program
* Reduced the number of `add_headers()` and `set_headers()` member variants, so that the user calls a templated version and the type is determined by the user's choice of arguments
* Made some `add_headers()` members protected, and suffixed with an `_` - the public variants call them
* Added ability to add a single named header to a program
* Reduced the number of `add_headers()` and `set_headers()` member variants, so that the user calls a templated version and the type is determined by the user's choice of arguments
* Made the lowest building-blocks of header-adding protected members, which the public variants call - for easier handling of types and catching of inappropriate argument type errors
* Added ability to add a single named header to a program
* Reduced the number of `add_headers()` and `set_headers()` member variants, so that the user calls a templated version and the type is determined by the user's choice of arguments
* Made the lowest building-blocks of header-adding protected members, which the public variants call - for easier handling of types and catching of inappropriate argument type errors
We already have multiple variants of
set_headers()
andadd_headers()
implemented. However - those templated variants which take containers or container pairs assume the element type is a constant C-style string of constant characters (const char* const
). What if the user has vectors ofstd::string
s? It's a legitimate scenario... let' cater to it.The text was updated successfully, but these errors were encountered: