Everyone knows that the best way to get something done on the Internet is with an inflammatory title and a potentially incorrect contention, so here goes.<\/p>\n\n\n\n
What do you if you want to capture\/log the filename of an assertion? Prior to C++20, you use good old After upgrading to C++20, you wonder if you can upgrade your logging\/assertion code to use But… now it doesn’t work. Because that’s not how your logging works. You’re working in embedded. No room for strings in your binary. Instead, you model your (statically-known) strings as types like You need strings to be types. You need to know the size at compile time. So you sadly accept that until and unless you get Of course the irony here is that Everyone knows that the best way to get something done on the Internet is with an inflammatory title and a potentially incorrect contention, so here goes. What do you if you want to capture\/log the filename of an assertion? Prior to C++20, you use good old __FILE__, which gives you…<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[22],"tags":[],"class_list":["post-1738","post","type-post","status-publish","format-standard","hentry","category-cpp"],"_links":{"self":[{"href":"https:\/\/www.elbeno.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/1738","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.elbeno.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.elbeno.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.elbeno.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.elbeno.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1738"}],"version-history":[{"count":2,"href":"https:\/\/www.elbeno.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/1738\/revisions"}],"predecessor-version":[{"id":1740,"href":"https:\/\/www.elbeno.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/1738\/revisions\/1740"}],"wp:attachment":[{"href":"https:\/\/www.elbeno.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1738"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.elbeno.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1738"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.elbeno.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1738"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}__FILE__<\/code>, which gives you a C-style array of char<\/code>s. But of course this is a macro, and means that your logging\/assertion code has to be a macro. With all the usual downsides of macros. Ho hum, that’s how it is for now, and it works. You go on your way.<\/p>\n\n\n\nstd::source_location<\/code>. Then maybe you could get rid of the macros. It looks odd at first, because you have to set it up as a default argument to your log function. But hey, this was someone’s clever solution to the problem, right? Obviously arguments are supplied at the call site, and default arguments are arguments, so they are too. So the std::source_location<\/code> default argument picks up the location of the call site, and you can grab the file_name<\/code> from it as a const char*<\/code>.<\/p>\n\n\n\nstring_constant<'H', 'e', 'l', 'l', 'o'><\/code>, you use nm<\/code> to extract the symbols from your library, and you generate tiny function specializations which turn the types into numbers, and melt away with LTO. (Like this.<\/a>)<\/p>\n\n\n\nstd::source_location::file_name()<\/code> gives you a const char*<\/code> – you don’t know the size of the string. And because it has to be a function argument, it can’t be constexpr<\/code>. There is no way to get back into type land. (At least, none that I know of yet, and believe me, I’ve tried. If you know how, let me know!) It’s the same story for the intrinsics that std::source_location<\/code> is built upon (__builtin_FILE_NAME<\/code>).<\/p>\n\n\n\njam tomorrow<\/s> another mechanism to do this, be it constexpr<\/code> function arguments or whatever, you’re stuck with __FILE__<\/code>, which works, because it gives you a sized<\/em> char<\/code> array which you can<\/em> turn into a type.<\/p>\n\n\n\nstd::source_location<\/code> provides information that is known only<\/em> at compile time. But we can’t use<\/em> that information fully at compile time, because it’s inadequately specified\/implemented.<\/p>\n","protected":false},"excerpt":{"rendered":"