| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
| |
Added 'static_cast<void>(parameter-name)' in all paths where the parameter isn't used
|
| |
|
|
|
|
|
|
|
|
|
| |
Tuples which are input data to std::tuple_cat() are not declared const.
Some versions of libc++ has a bug in std::tuple_cat(): All output
elements coming from a const tuple become const.
It can break 'make check' when using clang++ and -stdlib=libc++.
Fixes issue #25
|
|
|
|
|
|
| |
std::result_of is deprecated in C++17 and will be removed in C++20.
Fixes issue #19
|
|
|
|
|
| |
Update from murrayc-tuple-utils:
https://github.com/murraycu/murrayc-tuple-utils/commits/master
|
|
|
|
|
|
|
|
| |
From https://github.com/murraycu/murrayc-tuple-utils/commits/master
This also uses the C++17 nested namespace syntax.
Apart from tuple_transform_each, which seems to have a memory access
problem, with both g++ and clang++, in its C++17 version.
|
| |
|
|
|
|
|
|
|
|
|
| |
Apart from template template parameters, which must still be class
according to the C++14 standard:
http://stackoverflow.com/a/11311432/1123654
though g++ and clang++ actually already supporting using typename
instead by implementing N4051:
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4051.html
|
|
|
|
|
|
|
|
| |
This reverts commit 180353986d101e367c26b3199c44c7b2e4c1e681.
Because I misread https://stackoverflow.com/questions/213121/use-class-or-typename-for-template-parameters
class is _still_ needed for template template parameters in C++14,
though g++ and clang++ seem to support it anyway.
|
|
|
|
|
|
|
| |
For consistency. As of C++14 class is not necessary even
for template template parameters. We can change those few uses back
to class if any (otherwise compliant-enough) compiler actually needs it.
See http://stackoverflow.com/a/11311432/1123654
|
| |
|
|
|
|
|
|
|
|
| |
Following the change in their source in murrayc-tuple-utils.
I am the author, with some small improvements by Jonathan Wakely,
who agreed to the license change via email.
Bug #763616 (Dominique Leuenberger)
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Because we now motly only need the tuple*() utilities to manipulate
the actual instances. Some are still need for those tuple*()
implementations.
|
|
|
|
|
| |
tuple_transform_each() now iterates in order, instead of in reverse,
though that didn't seem to matter to how we used it in libsigc++.
|
|
|
|
| |
To discourage people from using libsigc++ just for the tuple utils.
|
|
|