As a security-critical component, QTextStream should have internal APIs that are hard to abuse. But there are error-prone (ptr, size) functions, which should be using views instead. And there's, in particular, the putString() overload set, which is "dangerous", since it contains (ptr, size, bool=false) and (view, bool) overloads which are prone to incorrectly resolve some (p, n) overloads towards the latter instead of the former (e.g. if the ptr isn't QChar, but something accepted by the view).

Acceptance criteria:

• replace (ptr, n) functions with ones taking view
• either replace the bool parameter by a tag struct, or split putString() into putString() and putNumber().