News for hackers. Stuff that matters.
Re:Just how constexpr is C++20’s std:string? by maccard on Friday September 08, 2023 @04:05PM (#37438733)
> If I want a string literal constant, I use string_view which can be constexp

That assumes your API accepts string views. How do you pass a string_view (safely) to fopen, or CreateFile (on windows)?

Re:Just how constexpr is C++20’s std:string? by eesmith on Friday September 08, 2023 @04:09PM (#37438767)
While (I think) I understand your broader point, when would you pass a string created by a constexp to fopen() or CreateFile?
Re:Just how constexpr is C++20’s std:string? by cshokie on Friday September 08, 2023 @04:58PM (#37439328)
Hard-coding a relative file path seems like an obvious example. For example a config file with settings. The file will always have the same name so heap allocations and mutability are not needed.
Re:Just how constexpr is C++20’s std:string? by eesmith on Saturday September 09, 2023 @12:31AM (#37442308)
My config file paths have either been constant (".dotfile") or required run-time information that could not be constexpr'ed. I don't see how constexpr would be useful.

Then again, I am primarily a Python and C programmer, so there is likely some underlying reasoning I'm missing.

Re:Just how constexpr is C++20’s std:string? by cshokie on Saturday September 09, 2023 @07:23PM (#37451289)
const std::string foo = “.dot file”;

in C++ cannot change after construction, but is not compile time constant. This means that it has to run some code and allocate some memory at runtime.

In contrast constexpr is fully compile time and ends up in the read only portion of the binary. No code code execution or allocations necessary.

Re:Just how constexpr is C++20’s std:string? by maccard on Friday September 08, 2023 @06:16PM (#37440022)
They were examples, they're widely used C apis. Anything that passes through to glibc, windows or posix will have this problem.
Re:Just how constexpr is C++20’s std:string? by eesmith on Saturday September 09, 2023 @12:26AM (#37442284)
I lack the intuition to understand why is it useful to constexpr path names. Could you elaborate?
Re:Just how constexpr is C++20’s std:string? by maccard on Saturday September 09, 2023 @04:00AM (#37443215)
It's not about path names. It's about passing constexpr strings to c functions that expect a null terminated string. You're totally missing the point.

That said, here's an example:

    // imagine this with string_view
    FILE* openFileInPath(const std::string& path) {
        
        if (path.starts_with("some_dir"))
        {
            return fopen(path.c_str());
        }
    return nullptr;
    }
That function works just fine to only open a path that has a prefix (logic bug on relative paths aside for brevity while posting)

I should be able to pass a constexpr string to that function the same way I can pass a runtime created string.

Re:Just how constexpr is C++20’s std:string? by eesmith on Saturday September 09, 2023 @07:54AM (#37444321)
Oh, I don't doubt I'm missing the point. That's why I'm asking. My C++ experience is from the 1990s. Otherwise I do Python and C.

I think of constexpr functions as something which occur at compile time, and I thought this linked-to piece was about what can take place inside those functions.

As I understand it, you want to create a constexpr string so it can be passed to a char*. The issue is this requires heap allocation (for large enough strings, based on the compiler implementation).

The C programmer in me wonders why you don't "char[]" allocate the static memory buffer, then pass around a string view, so the constexpr doesn't need heap at all.

Re:Just how constexpr is C++20’s std:string? by maccard on Saturday September 09, 2023 @09:00AM (#37444847)
> As I understand it, you want to create a constexpr string so it can be passed to a char*. The issue is this requires heap allocation (for large enough strings, based on the compiler implementation).

There's a few reasons. Avoiding the heap allocation is one, yep. There just shouldn't be a difference between a compile time string and a runtime string. As a programmer I don't want to have to deal with "which flavor of string am I dealing with".

The issue with passing to a c API (I used fopen, but think of any c library - zlib/gzip, openssl, sqlite) is that the string needs to be null terminated, and string view doesn't guarantee null termination.

    int foo(std::string_view view) {
        return strlen(view.data());
    }

    std::string str("hello world");
    foo(str):
    std::string_view view = str;
    foo(view);
    view.remove_suffix(6); // now view is just "hello" with no null termination
    foo(view); // this is wrong.
The problem isn't _specifically_ constexpr std::string in this case, it's that the tools that you use to generalise working with runtime strings, char buffers, and views aren't fit for purpose.
Re:Just how constexpr is C++20’s std:string? by eesmith on Saturday September 09, 2023 @11:26AM (#37446469)
Thank you for your detailed answer.

In the 1990s there was only one string type - NUL-terminated characters. ;)

I keep reading about all the neat algorithms (and multi-threading) support in modern C++, but the complexity of the decades of history and the difference in mindset between {C, Python} and C++ have made me shy away.

I think I'll keep mum from a distance in future discussions until I decided to (re) take up the language seriously.

Re:Just how constexpr is C++20’s std:string? by maccard on Saturday September 09, 2023 @02:26PM (#37448602)
> In the 1990s there was only one string type - NUL-terminated characters.

Indeed. If I could wave a magic wand, I would add a fat pointer to the language that we use to represent strings and arrays, and that we can automatically convert to/from const char* at compile time. This would replace string_view and span. All of the functionality of std::string would be available to it, and a call to strlen, or strcpy on it would work via the length, rather than the null terminator.

But alas, no magic wand.

Re:Just how constexpr is C++20’s std:string? by criddell on Friday September 08, 2023 @05:08PM (#37439458)
Old Windows APIs are a bit of a mess when it comes to const. So many that use LPWSTR strings rather than an LPCWSTR.