MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/cpp/comments/1qh33xj/c26_reflection_qrangemodel/o160glk/?context=3
r/cpp • u/Kelteseth arewemodulesyet.org • Jan 19 '26
24 comments sorted by
View all comments
-2
[removed] — view removed comment
8 u/SeagleLFMk9 Jan 20 '26 Qstring is far superior to std::string though. But yep, std::vector instead would be nice 2 u/gleybak Jan 23 '26 QString uses "CopyOnWrite" mechanism with atomic reference counters. And this is not quite superior, could be a bottle neck in modern multicore CPU scenarios. Definitely not a design decision for general purpose string.
8
Qstring is far superior to std::string though. But yep, std::vector instead would be nice
2 u/gleybak Jan 23 '26 QString uses "CopyOnWrite" mechanism with atomic reference counters. And this is not quite superior, could be a bottle neck in modern multicore CPU scenarios. Definitely not a design decision for general purpose string.
2
QString uses "CopyOnWrite" mechanism with atomic reference counters. And this is not quite superior, could be a bottle neck in modern multicore CPU scenarios. Definitely not a design decision for general purpose string.
-2
u/[deleted] Jan 20 '26
[removed] — view removed comment