Details
-
Task
-
Resolution: Fixed
-
P2: Important
-
None
-
None
-
5
-
590172ccc (dev), f0cb27f9f (6.5), c19f9716f (dev), 93cb61e30 (dev), 6a6e9337c (dev)
-
Foundation Sprint 77, Foundation Sprint 78
Description
See epic for rationale.
resultView() is already done.
Both the setData() calls and they key should be passed by QByteArrayView.
Acceptance criteria:
- the following API parts are ported to QByteArrayView:
- ctor (key)
- setKey()
- addData()
- 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?
Attachments
| For Gerrit Dashboard: QTBUG-111676 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 464036,2 | QMessageAuthenticationCode: port Private::setKey() to QByteArrayView | dev | qt/qtbase | Status: MERGED | +2 | 0 |
| 464065,5 | QMessageAuthenticationCode: port to QByteArrayView [1/3]: ctor/setKey() | dev | qt/qtbase | Status: MERGED | +2 | 0 |
| 464070,3 | QMessageAuthenticationCode: port to QByteArrayView [2/3]: addData() | dev | qt/qtbase | Status: MERGED | +2 | 0 |
| 464071,4 | QMessageAuthenticationCode: port to QByteArrayView [3/3]: static hash() | dev | qt/qtbase | Status: MERGED | +2 | 0 |
| 464161,2 | QMessageAuthenticationCode: port Private::setKey() to QByteArrayView | 6.5 | qt/qtbase | Status: MERGED | +2 | 0 |