See epic for rationale.
resultView() is already done.
Both the setData() calls and they key should be passed by QByteArrayView.
- the following API parts are ported to QByteArrayView:
- ctor (key)
- hash() (key and message)
We need to decide how to deal with the QBA->QBAV SiCs:
- accept, like in QCryptographicHash?
- make QBA Q_WEAK_OVERLOAD?
- make QBAV accept anything that implicitly converts to QBA, QAnyStringView-like?