What's new with QStringView; and how can it handle string processing with Qt.
summary
Qt 5.14 completes a richer QStringView and QLatin1String ecosystem so format and lookup APIs accept non-owning views and many literal types directly. The arg formatting becomes a multi-arg arg variadic template that accepts QStringView, QLatin1String and char16_t literals, cutting repeated conversions so a common case drops from several allocations to one allocation for the result. Split/tokenizer, formatted-number return types, UTF‑8 owning/view types and regex support remain work in progress.
AI-written summary · about
chapters (7)
- 0:00Start
- 2:19Api Patterns
- 24:46Solution Is Q String Tokenizer
- 25:37Template Arguments
- 26:19Object Lifetime
- 27:02Number Conversion Api
- 30:37Overview
related talks
22mRubyMotionQuery (RMQ) In Action
33mRefactoring Volatile Views into Cohesive Components
23mViews, from the top
37mKeynote: Herb to ReActionView: A New Foundation for the View Layer
57mViewComponents in the Real World
12mWriting Ruby Like it's 2018
59mMasterview
40mImprove extension API: C++ as better language for extension