3 ms·
The use after move existed prior, just wasn't moving even though they had written move. It is also written in a way that a linter should be able to detect if y
by TinkersW 4y ago
The use after move existed prior, just wasn't moving even though they had written move.
It is also written in a way that a linter should be able to detect if you disallow use after move.
https://source.chromium.org/chromium/chromium/src/+/main:components/services/storage/indexed_db/locks/disjoint_range_lock_manager.cc;l=136;drc=2705e1173e88110a9778b88a1c3e1be8d103f7e9 https://source.chromium.org/chromium/chromium/src/+/main:com...
- pkasting 4y agoIt's surprisingly hard to detect these sorts of cases reliably; we have a request out to the clang-tidy folks to add some improved detection of use-after-move there.