Consistent usage of template parameter namings
Dani-Hub opened this issue · 0 comments
Dani-Hub commented
The working paper consequently uses class instead of typename. I found the following deviations:
- [header.tuple.synop], [tuple.apply]:
template <typename F, typename Tuple>
constexpr decltype(auto) apply(F&& f, Tuple&& t);
- [any.synop], [any.cons], [any.assign], [any.nonmembers]:
template <typename ValueType>
any(ValueType&& value);
template <class Allocator, typename ValueType>
any(allocator_arg_t, const Allocator& a, ValueType&& value);
template <typename ValueType>
any& operator=(ValueType&& rhs);
template<typename ValueType>
ValueType any_cast(const any& operand);
template<typename ValueType>
ValueType any_cast(any& operand);
template<typename ValueType>
ValueType any_cast(any&& operand);
template<typename ValueType>
const ValueType* any_cast(const any* operand) noexcept;
template<typename ValueType>
ValueType* any_cast(any* operand) noexcept;
- [memory.polymorphic.allocator.overview], [memory.polymorphic.allocator.mem]:
template <typename T, typename... Args>
void construct(T* p, Args&&... args);
template <typename T>
void destroy(T* p);