this post was submitted on 01 Jan 2026
150 points (100.0% liked)
Programming
24240 readers
711 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
C++ already does that for short strings while seamlessly switching to allocation for long strings.
Also the case in the standard library
Iirc, that trick was used in one implementation but discontinued because it was against the standard.
If you need a niche for allocated string you can get to 254 but the typical choice seem to be around 16.
I've already been discussing this. Maybe read the rest of the thread.
I think you're missing the point of why. I built this to be a nearly drop in replacement for the standard string. If this wasn't the case it would need to do even more processing and work to pass the strings to anything.
Standards don't matter for an internal type that's not exposed to public APIs. I'm not trying to be exactly compatible with everything under the sun. There's no undefined behavior here so it's fine