How to use source_location in a variadic template function?Issue converting a macro with variable args (…) into constexpr variadic templateHow do you set, clear, and toggle a single bit?How do I iterate over the words of a string?Can templates only be implemented in header files?Calling a function for each variadic template argument and an arrayVariadic Template Parameter Packs with Alternating Typesstd::bind with variadic template functionVariadic Template Functions: No matching function for call, std::endlC++ errors with Variadic templateMixing const and non-const variables on variadic template
Adding things to bunches of things vs multiplication
Why was ramjet fuel used as hydraulic fluid during Saturn V checkout?
Saying something to a foreign coworker who uses "you people"
Does the Temple of the Gods spell nullify critical hits?
Why is the name Bergson pronounced like Berksonne?
How to use source_location in a variadic template function?
Would it be illegal for Facebook to actively promote a political agenda?
Independence of Mean and Variance of Discrete Uniform Distributions
Chess software to analyze games
Which basis does the wavefunction collapse to?
Do predators tend to have vertical slit pupils versus horizontal for prey animals?
Can the front glass be repaired of a broken lens?
Does git delete empty folders?
Why should P.I be willing to write strong LOR even if that means losing a undergraduate from his/her lab?
Do living authors still get paid royalties for their old work?
Are there reliable, formulaic ways to form chords on the guitar?
Why don't politicians push for fossil fuel reduction by pointing out their scarcity?
Build a mob of suspiciously happy lenny faces ( ͡° ͜ʖ ͡°)
My father gets angry everytime I pass Salam, that means I should stop saying Salam when he's around?
Designing a prison for a telekinetic race
How do we test and determine if a USB cable+connector is version 2, 3.0 or 3.1?
Why doesn't mathematics collapse down, even though humans quite often make mistakes in their proofs?
Are there categories whose internal hom is somewhat 'exotic'?
Best model for precedence constraints within scheduling problem
How to use source_location in a variadic template function?
Issue converting a macro with variable args (…) into constexpr variadic templateHow do you set, clear, and toggle a single bit?How do I iterate over the words of a string?Can templates only be implemented in header files?Calling a function for each variadic template argument and an arrayVariadic Template Parameter Packs with Alternating Typesstd::bind with variadic template functionVariadic Template Functions: No matching function for call, std::endlC++ errors with Variadic templateMixing const and non-const variables on variadic template
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
The C++20 feature std::source_location
is used to capture information about the context in which a function is called.
When I try to use it with a variadic template function, I encountered a problem: I can't see a place to put the source_location
parameter.
The following doesn't work because variadic parameters have to be at the end:
// doesn't work
template <typename... Args>
void debug(Args&&... args,
const std::source_location& loc = std::source_location::current());
The following doesn't work either because the caller will be screwed up by the parameter inserted in between:
// doesn't work either, because ...
template <typename... Args>
void debug(const std::source_location& loc = std::source_location::current(),
Args&&... args);
// the caller will get confused
debug(42); // error: cannot convert 42 to std::source_location
I was informed in a comment that std::source_location
works seamlessly with variadic templates, but I struggle to figure out how. How can I use std::source_location
with variadic template functions?
c++ variadic-templates c++20 default-arguments std-source-location
|
show 11 more comments
The C++20 feature std::source_location
is used to capture information about the context in which a function is called.
When I try to use it with a variadic template function, I encountered a problem: I can't see a place to put the source_location
parameter.
The following doesn't work because variadic parameters have to be at the end:
// doesn't work
template <typename... Args>
void debug(Args&&... args,
const std::source_location& loc = std::source_location::current());
The following doesn't work either because the caller will be screwed up by the parameter inserted in between:
// doesn't work either, because ...
template <typename... Args>
void debug(const std::source_location& loc = std::source_location::current(),
Args&&... args);
// the caller will get confused
debug(42); // error: cannot convert 42 to std::source_location
I was informed in a comment that std::source_location
works seamlessly with variadic templates, but I struggle to figure out how. How can I use std::source_location
with variadic template functions?
c++ variadic-templates c++20 default-arguments std-source-location
2
Perhaps makedebug
a macro that will call the real "debug" function with thestd::source_location::current()
call at the correct argument position (first)?
– Some programmer dude
8 hours ago
Regarding the removed comments that resulted in the edit: can't we have auto function arguments in templates in c++20?
– eerorika
8 hours ago
1
@Someprogrammerdude That will work correctly, but I consider that only a fallback if there's no better method. Using a macro defeats the purpose ofstd::source_location
in some way IMO :(
– L. F.
8 hours ago
@eerorika Yes,auto
is allowed in the parameter, but then we can provide42
or"foo"
as the source location.
– L. F.
8 hours ago
1
@NicolBolas You are right, being a regular object that can be passed around with its value unchanged is definitely an advantage of source_location. But I’d say the ability to get rid of macros is also an advantage, and that is the purpose I “intended” to defeat. Therefore I agree that the sentence is incomplet, but it is not incorrekt, is it? So it didn’t make much sense to me that it is nonsense. (I don’t know how to produce bad formatting here ...)
– L. F.
6 hours ago
|
show 11 more comments
The C++20 feature std::source_location
is used to capture information about the context in which a function is called.
When I try to use it with a variadic template function, I encountered a problem: I can't see a place to put the source_location
parameter.
The following doesn't work because variadic parameters have to be at the end:
// doesn't work
template <typename... Args>
void debug(Args&&... args,
const std::source_location& loc = std::source_location::current());
The following doesn't work either because the caller will be screwed up by the parameter inserted in between:
// doesn't work either, because ...
template <typename... Args>
void debug(const std::source_location& loc = std::source_location::current(),
Args&&... args);
// the caller will get confused
debug(42); // error: cannot convert 42 to std::source_location
I was informed in a comment that std::source_location
works seamlessly with variadic templates, but I struggle to figure out how. How can I use std::source_location
with variadic template functions?
c++ variadic-templates c++20 default-arguments std-source-location
The C++20 feature std::source_location
is used to capture information about the context in which a function is called.
When I try to use it with a variadic template function, I encountered a problem: I can't see a place to put the source_location
parameter.
The following doesn't work because variadic parameters have to be at the end:
// doesn't work
template <typename... Args>
void debug(Args&&... args,
const std::source_location& loc = std::source_location::current());
The following doesn't work either because the caller will be screwed up by the parameter inserted in between:
// doesn't work either, because ...
template <typename... Args>
void debug(const std::source_location& loc = std::source_location::current(),
Args&&... args);
// the caller will get confused
debug(42); // error: cannot convert 42 to std::source_location
I was informed in a comment that std::source_location
works seamlessly with variadic templates, but I struggle to figure out how. How can I use std::source_location
with variadic template functions?
c++ variadic-templates c++20 default-arguments std-source-location
c++ variadic-templates c++20 default-arguments std-source-location
edited 5 hours ago
einpoklum
42.3k28 gold badges147 silver badges292 bronze badges
42.3k28 gold badges147 silver badges292 bronze badges
asked 8 hours ago
L. F.L. F.
7,0175 gold badges19 silver badges45 bronze badges
7,0175 gold badges19 silver badges45 bronze badges
2
Perhaps makedebug
a macro that will call the real "debug" function with thestd::source_location::current()
call at the correct argument position (first)?
– Some programmer dude
8 hours ago
Regarding the removed comments that resulted in the edit: can't we have auto function arguments in templates in c++20?
– eerorika
8 hours ago
1
@Someprogrammerdude That will work correctly, but I consider that only a fallback if there's no better method. Using a macro defeats the purpose ofstd::source_location
in some way IMO :(
– L. F.
8 hours ago
@eerorika Yes,auto
is allowed in the parameter, but then we can provide42
or"foo"
as the source location.
– L. F.
8 hours ago
1
@NicolBolas You are right, being a regular object that can be passed around with its value unchanged is definitely an advantage of source_location. But I’d say the ability to get rid of macros is also an advantage, and that is the purpose I “intended” to defeat. Therefore I agree that the sentence is incomplet, but it is not incorrekt, is it? So it didn’t make much sense to me that it is nonsense. (I don’t know how to produce bad formatting here ...)
– L. F.
6 hours ago
|
show 11 more comments
2
Perhaps makedebug
a macro that will call the real "debug" function with thestd::source_location::current()
call at the correct argument position (first)?
– Some programmer dude
8 hours ago
Regarding the removed comments that resulted in the edit: can't we have auto function arguments in templates in c++20?
– eerorika
8 hours ago
1
@Someprogrammerdude That will work correctly, but I consider that only a fallback if there's no better method. Using a macro defeats the purpose ofstd::source_location
in some way IMO :(
– L. F.
8 hours ago
@eerorika Yes,auto
is allowed in the parameter, but then we can provide42
or"foo"
as the source location.
– L. F.
8 hours ago
1
@NicolBolas You are right, being a regular object that can be passed around with its value unchanged is definitely an advantage of source_location. But I’d say the ability to get rid of macros is also an advantage, and that is the purpose I “intended” to defeat. Therefore I agree that the sentence is incomplet, but it is not incorrekt, is it? So it didn’t make much sense to me that it is nonsense. (I don’t know how to produce bad formatting here ...)
– L. F.
6 hours ago
2
2
Perhaps make
debug
a macro that will call the real "debug" function with the std::source_location::current()
call at the correct argument position (first)?– Some programmer dude
8 hours ago
Perhaps make
debug
a macro that will call the real "debug" function with the std::source_location::current()
call at the correct argument position (first)?– Some programmer dude
8 hours ago
Regarding the removed comments that resulted in the edit: can't we have auto function arguments in templates in c++20?
– eerorika
8 hours ago
Regarding the removed comments that resulted in the edit: can't we have auto function arguments in templates in c++20?
– eerorika
8 hours ago
1
1
@Someprogrammerdude That will work correctly, but I consider that only a fallback if there's no better method. Using a macro defeats the purpose of
std::source_location
in some way IMO :(– L. F.
8 hours ago
@Someprogrammerdude That will work correctly, but I consider that only a fallback if there's no better method. Using a macro defeats the purpose of
std::source_location
in some way IMO :(– L. F.
8 hours ago
@eerorika Yes,
auto
is allowed in the parameter, but then we can provide 42
or "foo"
as the source location.– L. F.
8 hours ago
@eerorika Yes,
auto
is allowed in the parameter, but then we can provide 42
or "foo"
as the source location.– L. F.
8 hours ago
1
1
@NicolBolas You are right, being a regular object that can be passed around with its value unchanged is definitely an advantage of source_location. But I’d say the ability to get rid of macros is also an advantage, and that is the purpose I “intended” to defeat. Therefore I agree that the sentence is incomplet, but it is not incorrekt, is it? So it didn’t make much sense to me that it is nonsense. (I don’t know how to produce bad formatting here ...)
– L. F.
6 hours ago
@NicolBolas You are right, being a regular object that can be passed around with its value unchanged is definitely an advantage of source_location. But I’d say the ability to get rid of macros is also an advantage, and that is the purpose I “intended” to defeat. Therefore I agree that the sentence is incomplet, but it is not incorrekt, is it? So it didn’t make much sense to me that it is nonsense. (I don’t know how to produce bad formatting here ...)
– L. F.
6 hours ago
|
show 11 more comments
4 Answers
4
active
oldest
votes
template <typename... Ts>
struct debug
debug(Ts&&... ts, const std::source_location& loc = std::source_location::current());
;
template <typename... Ts>
debug(Ts&&...) -> debug<Ts...>;
Test:
int main()
debug(5, 'A', 3.14f, "foo");
DEMO
2
Great! This is the most elegant solution so far! Such creative usage of deduction guides
– L. F.
5 hours ago
add a comment |
template <typename... Args>
void debug(Args&&... args,
const std::source_location& loc = std::source_location::current());
"works", but requires to specify template arguments as there are non deducible as there are not last:
debug<int>(42);
Demo
Possible (not perfect) alternatives include:
use overloads with hard coded limit (old possible way to "handle" variadic):
// 0 arguments
void debug(const std::source_location& loc = std::source_location::current());
// 1 argument
template <typename T0>
void debug(T0&& t0,
const std::source_location& loc = std::source_location::current());
// 2 arguments
template <typename T0, typename T1>
void debug(T0&& t0, T1&& t1,
const std::source_location& loc = std::source_location::current());
// ...Demo
to put
source_location
at first position, without default:template <typename... Args>
void debug(const std::source_location& loc, Args&&... args);and
debug(std::source_location::current(), 42);
Demo
similarly to overloads, but just use tuple as group
template <typename Tuple>
void debug(Tuple&& t,
const std::source_location& loc = std::source_location::current());or
template <typename ... Ts>
void debug(const std::tuple<Ts...>& t,
const std::source_location& loc = std::source_location::current());with usage
debug(std::make_tuple(42));
Demo
I like your first alternative the best. While it's ugly code, it's the most convenient to use, and that's what's most important.
– einpoklum
5 hours ago
add a comment |
Not a great solution but... what about place the variadic arguments in a std::tuple
?
I mean... something as
template <typename... Args>
void debug (std::tuple<Args...> && t_args,
std::source_location const & loc = std::source_location::current());
Unfortunately, this way you have to explicitly call std::make_tuple
calling it
debug(std::make_tuple(1, 2l, 3ll));
1
@L.F. - sorry: maybe I've misunderstood: do you mean that do you want substitute a variadic macro with a template variadic function?
– max66
8 hours ago
My original question doesn’t make sense at all. I have updated my question to make the actual question stand out. Ignore the variadic macros. Sorry!
– L. F.
7 hours ago
@L.F. - I see... well, my answer remain almost the same but the needs of explicitly callstd::make_tuple()
make it less interesting.
– max66
7 hours ago
add a comment |
Just put your arguments in a tuple, no macro needed.
#include <source_location>
#include <tuple>
template <typename... Args>
void debug(
std::tuple<Args...> args,
const std::source_location& loc = std::source_location::current())
std::cout
<< "debug() called from source location "
<< loc.file_name() << ":" << loc.line() << 'n';
And this works*.
Technically you could just write:
template <typename T>
void debug(
T arg,
const std::source_location& loc = std::source_location::current())
std::cout
<< "debug() called from source location "
<< loc.file_name() << ":" << loc.line() << 'n';
but then you'd probably have to jump through some hoops to get the argument types.
* In the linked-to example, I'm using <experimental/source_location>
because that's what compilers accept right now. Also, I added some code for printing the argument tuple.
1
"this works just fine" You mean, besides the fact that you have to put the values in a tuple? And therefore have to deal with a lot of pointless syntax to actually extract and use them for their intended purpose?
– Nicol Bolas
7 hours ago
@NicolBolas: s/a lot of/a bit of/ ; But - see edit.
– einpoklum
7 hours ago
That all depends on what you're doing with them. In a variadic template, formatting all of the values to a stream is trivial and easily readable. In your version, it is neither. It's doable, but not pretty.
– Nicol Bolas
7 hours ago
@NicolBolas: You might prefer that, but I would say it is just stylistic "problem" to iterate over tuple/variadic template.
– Jarod42
6 hours ago
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f57547273%2fhow-to-use-source-location-in-a-variadic-template-function%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
template <typename... Ts>
struct debug
debug(Ts&&... ts, const std::source_location& loc = std::source_location::current());
;
template <typename... Ts>
debug(Ts&&...) -> debug<Ts...>;
Test:
int main()
debug(5, 'A', 3.14f, "foo");
DEMO
2
Great! This is the most elegant solution so far! Such creative usage of deduction guides
– L. F.
5 hours ago
add a comment |
template <typename... Ts>
struct debug
debug(Ts&&... ts, const std::source_location& loc = std::source_location::current());
;
template <typename... Ts>
debug(Ts&&...) -> debug<Ts...>;
Test:
int main()
debug(5, 'A', 3.14f, "foo");
DEMO
2
Great! This is the most elegant solution so far! Such creative usage of deduction guides
– L. F.
5 hours ago
add a comment |
template <typename... Ts>
struct debug
debug(Ts&&... ts, const std::source_location& loc = std::source_location::current());
;
template <typename... Ts>
debug(Ts&&...) -> debug<Ts...>;
Test:
int main()
debug(5, 'A', 3.14f, "foo");
DEMO
template <typename... Ts>
struct debug
debug(Ts&&... ts, const std::source_location& loc = std::source_location::current());
;
template <typename... Ts>
debug(Ts&&...) -> debug<Ts...>;
Test:
int main()
debug(5, 'A', 3.14f, "foo");
DEMO
answered 5 hours ago
Piotr SkotnickiPiotr Skotnicki
36.1k4 gold badges75 silver badges123 bronze badges
36.1k4 gold badges75 silver badges123 bronze badges
2
Great! This is the most elegant solution so far! Such creative usage of deduction guides
– L. F.
5 hours ago
add a comment |
2
Great! This is the most elegant solution so far! Such creative usage of deduction guides
– L. F.
5 hours ago
2
2
Great! This is the most elegant solution so far! Such creative usage of deduction guides
– L. F.
5 hours ago
Great! This is the most elegant solution so far! Such creative usage of deduction guides
– L. F.
5 hours ago
add a comment |
template <typename... Args>
void debug(Args&&... args,
const std::source_location& loc = std::source_location::current());
"works", but requires to specify template arguments as there are non deducible as there are not last:
debug<int>(42);
Demo
Possible (not perfect) alternatives include:
use overloads with hard coded limit (old possible way to "handle" variadic):
// 0 arguments
void debug(const std::source_location& loc = std::source_location::current());
// 1 argument
template <typename T0>
void debug(T0&& t0,
const std::source_location& loc = std::source_location::current());
// 2 arguments
template <typename T0, typename T1>
void debug(T0&& t0, T1&& t1,
const std::source_location& loc = std::source_location::current());
// ...Demo
to put
source_location
at first position, without default:template <typename... Args>
void debug(const std::source_location& loc, Args&&... args);and
debug(std::source_location::current(), 42);
Demo
similarly to overloads, but just use tuple as group
template <typename Tuple>
void debug(Tuple&& t,
const std::source_location& loc = std::source_location::current());or
template <typename ... Ts>
void debug(const std::tuple<Ts...>& t,
const std::source_location& loc = std::source_location::current());with usage
debug(std::make_tuple(42));
Demo
I like your first alternative the best. While it's ugly code, it's the most convenient to use, and that's what's most important.
– einpoklum
5 hours ago
add a comment |
template <typename... Args>
void debug(Args&&... args,
const std::source_location& loc = std::source_location::current());
"works", but requires to specify template arguments as there are non deducible as there are not last:
debug<int>(42);
Demo
Possible (not perfect) alternatives include:
use overloads with hard coded limit (old possible way to "handle" variadic):
// 0 arguments
void debug(const std::source_location& loc = std::source_location::current());
// 1 argument
template <typename T0>
void debug(T0&& t0,
const std::source_location& loc = std::source_location::current());
// 2 arguments
template <typename T0, typename T1>
void debug(T0&& t0, T1&& t1,
const std::source_location& loc = std::source_location::current());
// ...Demo
to put
source_location
at first position, without default:template <typename... Args>
void debug(const std::source_location& loc, Args&&... args);and
debug(std::source_location::current(), 42);
Demo
similarly to overloads, but just use tuple as group
template <typename Tuple>
void debug(Tuple&& t,
const std::source_location& loc = std::source_location::current());or
template <typename ... Ts>
void debug(const std::tuple<Ts...>& t,
const std::source_location& loc = std::source_location::current());with usage
debug(std::make_tuple(42));
Demo
I like your first alternative the best. While it's ugly code, it's the most convenient to use, and that's what's most important.
– einpoklum
5 hours ago
add a comment |
template <typename... Args>
void debug(Args&&... args,
const std::source_location& loc = std::source_location::current());
"works", but requires to specify template arguments as there are non deducible as there are not last:
debug<int>(42);
Demo
Possible (not perfect) alternatives include:
use overloads with hard coded limit (old possible way to "handle" variadic):
// 0 arguments
void debug(const std::source_location& loc = std::source_location::current());
// 1 argument
template <typename T0>
void debug(T0&& t0,
const std::source_location& loc = std::source_location::current());
// 2 arguments
template <typename T0, typename T1>
void debug(T0&& t0, T1&& t1,
const std::source_location& loc = std::source_location::current());
// ...Demo
to put
source_location
at first position, without default:template <typename... Args>
void debug(const std::source_location& loc, Args&&... args);and
debug(std::source_location::current(), 42);
Demo
similarly to overloads, but just use tuple as group
template <typename Tuple>
void debug(Tuple&& t,
const std::source_location& loc = std::source_location::current());or
template <typename ... Ts>
void debug(const std::tuple<Ts...>& t,
const std::source_location& loc = std::source_location::current());with usage
debug(std::make_tuple(42));
Demo
template <typename... Args>
void debug(Args&&... args,
const std::source_location& loc = std::source_location::current());
"works", but requires to specify template arguments as there are non deducible as there are not last:
debug<int>(42);
Demo
Possible (not perfect) alternatives include:
use overloads with hard coded limit (old possible way to "handle" variadic):
// 0 arguments
void debug(const std::source_location& loc = std::source_location::current());
// 1 argument
template <typename T0>
void debug(T0&& t0,
const std::source_location& loc = std::source_location::current());
// 2 arguments
template <typename T0, typename T1>
void debug(T0&& t0, T1&& t1,
const std::source_location& loc = std::source_location::current());
// ...Demo
to put
source_location
at first position, without default:template <typename... Args>
void debug(const std::source_location& loc, Args&&... args);and
debug(std::source_location::current(), 42);
Demo
similarly to overloads, but just use tuple as group
template <typename Tuple>
void debug(Tuple&& t,
const std::source_location& loc = std::source_location::current());or
template <typename ... Ts>
void debug(const std::tuple<Ts...>& t,
const std::source_location& loc = std::source_location::current());with usage
debug(std::make_tuple(42));
Demo
edited 7 hours ago
answered 7 hours ago
Jarod42Jarod42
129k12 gold badges114 silver badges202 bronze badges
129k12 gold badges114 silver badges202 bronze badges
I like your first alternative the best. While it's ugly code, it's the most convenient to use, and that's what's most important.
– einpoklum
5 hours ago
add a comment |
I like your first alternative the best. While it's ugly code, it's the most convenient to use, and that's what's most important.
– einpoklum
5 hours ago
I like your first alternative the best. While it's ugly code, it's the most convenient to use, and that's what's most important.
– einpoklum
5 hours ago
I like your first alternative the best. While it's ugly code, it's the most convenient to use, and that's what's most important.
– einpoklum
5 hours ago
add a comment |
Not a great solution but... what about place the variadic arguments in a std::tuple
?
I mean... something as
template <typename... Args>
void debug (std::tuple<Args...> && t_args,
std::source_location const & loc = std::source_location::current());
Unfortunately, this way you have to explicitly call std::make_tuple
calling it
debug(std::make_tuple(1, 2l, 3ll));
1
@L.F. - sorry: maybe I've misunderstood: do you mean that do you want substitute a variadic macro with a template variadic function?
– max66
8 hours ago
My original question doesn’t make sense at all. I have updated my question to make the actual question stand out. Ignore the variadic macros. Sorry!
– L. F.
7 hours ago
@L.F. - I see... well, my answer remain almost the same but the needs of explicitly callstd::make_tuple()
make it less interesting.
– max66
7 hours ago
add a comment |
Not a great solution but... what about place the variadic arguments in a std::tuple
?
I mean... something as
template <typename... Args>
void debug (std::tuple<Args...> && t_args,
std::source_location const & loc = std::source_location::current());
Unfortunately, this way you have to explicitly call std::make_tuple
calling it
debug(std::make_tuple(1, 2l, 3ll));
1
@L.F. - sorry: maybe I've misunderstood: do you mean that do you want substitute a variadic macro with a template variadic function?
– max66
8 hours ago
My original question doesn’t make sense at all. I have updated my question to make the actual question stand out. Ignore the variadic macros. Sorry!
– L. F.
7 hours ago
@L.F. - I see... well, my answer remain almost the same but the needs of explicitly callstd::make_tuple()
make it less interesting.
– max66
7 hours ago
add a comment |
Not a great solution but... what about place the variadic arguments in a std::tuple
?
I mean... something as
template <typename... Args>
void debug (std::tuple<Args...> && t_args,
std::source_location const & loc = std::source_location::current());
Unfortunately, this way you have to explicitly call std::make_tuple
calling it
debug(std::make_tuple(1, 2l, 3ll));
Not a great solution but... what about place the variadic arguments in a std::tuple
?
I mean... something as
template <typename... Args>
void debug (std::tuple<Args...> && t_args,
std::source_location const & loc = std::source_location::current());
Unfortunately, this way you have to explicitly call std::make_tuple
calling it
debug(std::make_tuple(1, 2l, 3ll));
edited 7 hours ago
answered 8 hours ago
max66max66
44.7k7 gold badges48 silver badges78 bronze badges
44.7k7 gold badges48 silver badges78 bronze badges
1
@L.F. - sorry: maybe I've misunderstood: do you mean that do you want substitute a variadic macro with a template variadic function?
– max66
8 hours ago
My original question doesn’t make sense at all. I have updated my question to make the actual question stand out. Ignore the variadic macros. Sorry!
– L. F.
7 hours ago
@L.F. - I see... well, my answer remain almost the same but the needs of explicitly callstd::make_tuple()
make it less interesting.
– max66
7 hours ago
add a comment |
1
@L.F. - sorry: maybe I've misunderstood: do you mean that do you want substitute a variadic macro with a template variadic function?
– max66
8 hours ago
My original question doesn’t make sense at all. I have updated my question to make the actual question stand out. Ignore the variadic macros. Sorry!
– L. F.
7 hours ago
@L.F. - I see... well, my answer remain almost the same but the needs of explicitly callstd::make_tuple()
make it less interesting.
– max66
7 hours ago
1
1
@L.F. - sorry: maybe I've misunderstood: do you mean that do you want substitute a variadic macro with a template variadic function?
– max66
8 hours ago
@L.F. - sorry: maybe I've misunderstood: do you mean that do you want substitute a variadic macro with a template variadic function?
– max66
8 hours ago
My original question doesn’t make sense at all. I have updated my question to make the actual question stand out. Ignore the variadic macros. Sorry!
– L. F.
7 hours ago
My original question doesn’t make sense at all. I have updated my question to make the actual question stand out. Ignore the variadic macros. Sorry!
– L. F.
7 hours ago
@L.F. - I see... well, my answer remain almost the same but the needs of explicitly call
std::make_tuple()
make it less interesting.– max66
7 hours ago
@L.F. - I see... well, my answer remain almost the same but the needs of explicitly call
std::make_tuple()
make it less interesting.– max66
7 hours ago
add a comment |
Just put your arguments in a tuple, no macro needed.
#include <source_location>
#include <tuple>
template <typename... Args>
void debug(
std::tuple<Args...> args,
const std::source_location& loc = std::source_location::current())
std::cout
<< "debug() called from source location "
<< loc.file_name() << ":" << loc.line() << 'n';
And this works*.
Technically you could just write:
template <typename T>
void debug(
T arg,
const std::source_location& loc = std::source_location::current())
std::cout
<< "debug() called from source location "
<< loc.file_name() << ":" << loc.line() << 'n';
but then you'd probably have to jump through some hoops to get the argument types.
* In the linked-to example, I'm using <experimental/source_location>
because that's what compilers accept right now. Also, I added some code for printing the argument tuple.
1
"this works just fine" You mean, besides the fact that you have to put the values in a tuple? And therefore have to deal with a lot of pointless syntax to actually extract and use them for their intended purpose?
– Nicol Bolas
7 hours ago
@NicolBolas: s/a lot of/a bit of/ ; But - see edit.
– einpoklum
7 hours ago
That all depends on what you're doing with them. In a variadic template, formatting all of the values to a stream is trivial and easily readable. In your version, it is neither. It's doable, but not pretty.
– Nicol Bolas
7 hours ago
@NicolBolas: You might prefer that, but I would say it is just stylistic "problem" to iterate over tuple/variadic template.
– Jarod42
6 hours ago
add a comment |
Just put your arguments in a tuple, no macro needed.
#include <source_location>
#include <tuple>
template <typename... Args>
void debug(
std::tuple<Args...> args,
const std::source_location& loc = std::source_location::current())
std::cout
<< "debug() called from source location "
<< loc.file_name() << ":" << loc.line() << 'n';
And this works*.
Technically you could just write:
template <typename T>
void debug(
T arg,
const std::source_location& loc = std::source_location::current())
std::cout
<< "debug() called from source location "
<< loc.file_name() << ":" << loc.line() << 'n';
but then you'd probably have to jump through some hoops to get the argument types.
* In the linked-to example, I'm using <experimental/source_location>
because that's what compilers accept right now. Also, I added some code for printing the argument tuple.
1
"this works just fine" You mean, besides the fact that you have to put the values in a tuple? And therefore have to deal with a lot of pointless syntax to actually extract and use them for their intended purpose?
– Nicol Bolas
7 hours ago
@NicolBolas: s/a lot of/a bit of/ ; But - see edit.
– einpoklum
7 hours ago
That all depends on what you're doing with them. In a variadic template, formatting all of the values to a stream is trivial and easily readable. In your version, it is neither. It's doable, but not pretty.
– Nicol Bolas
7 hours ago
@NicolBolas: You might prefer that, but I would say it is just stylistic "problem" to iterate over tuple/variadic template.
– Jarod42
6 hours ago
add a comment |
Just put your arguments in a tuple, no macro needed.
#include <source_location>
#include <tuple>
template <typename... Args>
void debug(
std::tuple<Args...> args,
const std::source_location& loc = std::source_location::current())
std::cout
<< "debug() called from source location "
<< loc.file_name() << ":" << loc.line() << 'n';
And this works*.
Technically you could just write:
template <typename T>
void debug(
T arg,
const std::source_location& loc = std::source_location::current())
std::cout
<< "debug() called from source location "
<< loc.file_name() << ":" << loc.line() << 'n';
but then you'd probably have to jump through some hoops to get the argument types.
* In the linked-to example, I'm using <experimental/source_location>
because that's what compilers accept right now. Also, I added some code for printing the argument tuple.
Just put your arguments in a tuple, no macro needed.
#include <source_location>
#include <tuple>
template <typename... Args>
void debug(
std::tuple<Args...> args,
const std::source_location& loc = std::source_location::current())
std::cout
<< "debug() called from source location "
<< loc.file_name() << ":" << loc.line() << 'n';
And this works*.
Technically you could just write:
template <typename T>
void debug(
T arg,
const std::source_location& loc = std::source_location::current())
std::cout
<< "debug() called from source location "
<< loc.file_name() << ":" << loc.line() << 'n';
but then you'd probably have to jump through some hoops to get the argument types.
* In the linked-to example, I'm using <experimental/source_location>
because that's what compilers accept right now. Also, I added some code for printing the argument tuple.
edited 7 hours ago
answered 7 hours ago
einpoklumeinpoklum
42.3k28 gold badges147 silver badges292 bronze badges
42.3k28 gold badges147 silver badges292 bronze badges
1
"this works just fine" You mean, besides the fact that you have to put the values in a tuple? And therefore have to deal with a lot of pointless syntax to actually extract and use them for their intended purpose?
– Nicol Bolas
7 hours ago
@NicolBolas: s/a lot of/a bit of/ ; But - see edit.
– einpoklum
7 hours ago
That all depends on what you're doing with them. In a variadic template, formatting all of the values to a stream is trivial and easily readable. In your version, it is neither. It's doable, but not pretty.
– Nicol Bolas
7 hours ago
@NicolBolas: You might prefer that, but I would say it is just stylistic "problem" to iterate over tuple/variadic template.
– Jarod42
6 hours ago
add a comment |
1
"this works just fine" You mean, besides the fact that you have to put the values in a tuple? And therefore have to deal with a lot of pointless syntax to actually extract and use them for their intended purpose?
– Nicol Bolas
7 hours ago
@NicolBolas: s/a lot of/a bit of/ ; But - see edit.
– einpoklum
7 hours ago
That all depends on what you're doing with them. In a variadic template, formatting all of the values to a stream is trivial and easily readable. In your version, it is neither. It's doable, but not pretty.
– Nicol Bolas
7 hours ago
@NicolBolas: You might prefer that, but I would say it is just stylistic "problem" to iterate over tuple/variadic template.
– Jarod42
6 hours ago
1
1
"this works just fine" You mean, besides the fact that you have to put the values in a tuple? And therefore have to deal with a lot of pointless syntax to actually extract and use them for their intended purpose?
– Nicol Bolas
7 hours ago
"this works just fine" You mean, besides the fact that you have to put the values in a tuple? And therefore have to deal with a lot of pointless syntax to actually extract and use them for their intended purpose?
– Nicol Bolas
7 hours ago
@NicolBolas: s/a lot of/a bit of/ ; But - see edit.
– einpoklum
7 hours ago
@NicolBolas: s/a lot of/a bit of/ ; But - see edit.
– einpoklum
7 hours ago
That all depends on what you're doing with them. In a variadic template, formatting all of the values to a stream is trivial and easily readable. In your version, it is neither. It's doable, but not pretty.
– Nicol Bolas
7 hours ago
That all depends on what you're doing with them. In a variadic template, formatting all of the values to a stream is trivial and easily readable. In your version, it is neither. It's doable, but not pretty.
– Nicol Bolas
7 hours ago
@NicolBolas: You might prefer that, but I would say it is just stylistic "problem" to iterate over tuple/variadic template.
– Jarod42
6 hours ago
@NicolBolas: You might prefer that, but I would say it is just stylistic "problem" to iterate over tuple/variadic template.
– Jarod42
6 hours ago
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f57547273%2fhow-to-use-source-location-in-a-variadic-template-function%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
Perhaps make
debug
a macro that will call the real "debug" function with thestd::source_location::current()
call at the correct argument position (first)?– Some programmer dude
8 hours ago
Regarding the removed comments that resulted in the edit: can't we have auto function arguments in templates in c++20?
– eerorika
8 hours ago
1
@Someprogrammerdude That will work correctly, but I consider that only a fallback if there's no better method. Using a macro defeats the purpose of
std::source_location
in some way IMO :(– L. F.
8 hours ago
@eerorika Yes,
auto
is allowed in the parameter, but then we can provide42
or"foo"
as the source location.– L. F.
8 hours ago
1
@NicolBolas You are right, being a regular object that can be passed around with its value unchanged is definitely an advantage of source_location. But I’d say the ability to get rid of macros is also an advantage, and that is the purpose I “intended” to defeat. Therefore I agree that the sentence is incomplet, but it is not incorrekt, is it? So it didn’t make much sense to me that it is nonsense. (I don’t know how to produce bad formatting here ...)
– L. F.
6 hours ago