commit | 5f230f8442e0680aeea247d382718ed97c6bffd5 | [log] [tgz] |
---|---|---|
author | Daniel Cheng <dcheng@chromium.org> | Tue Jun 14 21:41:29 2022 |
committer | Prudhvikumar Bommana <pbommana@google.com> | Tue Jun 14 21:41:29 2022 |
tree | ab5db9c0e1a9be7a678e959df148d546b247965b | |
parent | 76968bbba26a825e0e0cdae1ae1cc90c0cc87d74 [diff] |
[M103] Ensure raw_ptr<T> and T* are treated identically in //base callback. There are safety checks associated with raw pointers (e.g. ensuring receiver pointers are not raw pointers). Make sure these checks are applied whether the input type is T* or raw_ptr<T>. - Implement base::IsPointer<T> and base::RemovePointer<T>, which are similar to std::is_pointer<T> and std::remove_pointer<T>, except they also consider raw_ptr<T> a raw pointer type. - Fix failures from the strengthened asserts: WebAppInstallFinalizer does not need a callback at all, while the privacy sandbox dialog tests can safely use base::Unretained(). - Add test cases to cover this in the //base callback nocompile test suite. - Fix the existing nocompile tests, which did not escape `||` and inadvertently matched any error text. (cherry picked from commit 00c072a2c7f24921af3bbf8441abb34ecb0551a6) Bug: 1335458 Change-Id: I470e3d5bc35ed52bf125136db738a868ef90b7e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3700700 Reviewed-by: Lei Zhang <thestig@chromium.org> Commit-Queue: Daniel Cheng <dcheng@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1013266} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3703540 Commit-Queue: Prudhvikumar Bommana <pbommana@google.com> Cr-Commit-Position: refs/branch-heads/5060@{#848} Cr-Branched-From: b83393d0f4038aeaf67f970a024d8101df7348d1-refs/heads/main@{#1002911}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.