In this example, is it possible to allow the deduction of the template parameters type of the tuple
?
#include<tuple>
#include<string>
template<class T1, class T2>
void fun(std::tuple<T1, T2> t, std::string other){}
int main(){
fun(std::tuple<double, int>(2.,3), std::string("other")); // ok
fun(std::make_tuple(2.,3), std::string("other")); // ok, but trying to avoid `make_tuple`
fun({2.,3},std::string("other")); // desired syntax but
// giving compilation error: candidate template ignored: couldn't infer template argument 'T1' void fun(std::tuple<T1, T2> t)
}
I added the second argument other
to avoid solutions involving variadic arguments at the level of the function fun
. Also, I am trying to avoid the use of make_tuple
, at least from the user code (i.e. in main()
). In fact it doesn't need to be the tuple
type the one involved as long as the "desired syntax" is allowed and somehow its element types can be deduced at later stage.
(Also, although similar, this has nothing to do with initializer_list
since it doesn't work at all having dissimilar elements in the braces)
It fails at least with clang 3.2
and gcc 4.7.2
. Is there any hope that it would work with the current or a near-future standard? (e.g. a future(?) initializer_tuple
.)
(This can be very useful to add expressiveness to function calls, by aggregating subelements, but that can be argued about)
Note: For the example code it seems that std::forward_as_tuple
is more appropriate than std::make_tuple
so the arguments are not necessarily copied: http://en.cppreference.com/w/cpp/utility/tuple/forward_as_tuple . Still not as nice as if there were a build-in language feature for heterogeneous initializer lists.