|
|
Created:
4 years ago by meade_UTC10 Modified:
4 years ago Reviewers:
sashab CC:
darktears, apavlov+blink_chromium.org, blink-reviews, blink-reviews-css, blink-reviews-style_chromium.org, chromium-reviews, dglazkov+blink, rwlbuis Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionMove pure functions in CSSComputedStyleDeclaration.cpp into their own private namespace.
This prevents naming conflicts in the blink namespace, which could have
unexpected results.
Committed: https://crrev.com/714706d0823bdd021e8fd68221f635dd2ab8264b
Cr-Commit-Position: refs/heads/master@{#437394}
Patch Set 1 #Patch Set 2 : Remove extra static keywords #Messages
Total messages: 18 (10 generated)
meade@chromium.org changed reviewers: + sashab@chromium.org
Hey Sasha! I noticed this when reviewing a CL. Do you think it's a good idea?
The CQ bit was checked by meade@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Haha sure! Putting the static keyword in front of a method is equivalent to putting them in a private namespace, but private namespaces are more C++-y. Remove the static keyword from in front of the methods you moved because you shouldn't have both. Other than that lgtm :)
Patchset #2 (id:20001) has been deleted
On 2016/12/08 05:36:45, sashab wrote: > Haha sure! Putting the static keyword in front of a method is equivalent to > putting them in a private namespace, but private namespaces are more C++-y. > > Remove the static keyword from in front of the methods you moved because you > shouldn't have both. Other than that lgtm :) Ah yep. It's def better to use the private namespace since you definitely can't get naming conflicts that way (although you'd know since it'd be a compile error). Thanks!
The CQ bit was checked by meade@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from sashab@chromium.org Link to the patchset: https://codereview.chromium.org/2552893006/#ps40001 (title: "Remove extra static keywords")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: android_n5x_swarming_rel on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/android_n5x_...)
The CQ bit was checked by meade@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
CQ is committing da patch. Bot data: {"patchset_id": 40001, "attempt_start_ts": 1481236091111310, "parent_rev": "5e353c0e9add38bd3aa1d99b3d598e66bbfcbcce", "commit_rev": "a2fcd483f9fe76354b377c032c531086c6805f7f"}
Message was sent while issue was closed.
Committed patchset #2 (id:40001)
Message was sent while issue was closed.
Description was changed from ========== Move pure functions in CSSComputedStyleDeclaration.cpp into their own private namespace. This prevents naming conflicts in the blink namespace, which could have unexpected results. ========== to ========== Move pure functions in CSSComputedStyleDeclaration.cpp into their own private namespace. This prevents naming conflicts in the blink namespace, which could have unexpected results. Committed: https://crrev.com/714706d0823bdd021e8fd68221f635dd2ab8264b Cr-Commit-Position: refs/heads/master@{#437394} ==========
Message was sent while issue was closed.
Patchset 2 (id:??) landed as https://crrev.com/714706d0823bdd021e8fd68221f635dd2ab8264b Cr-Commit-Position: refs/heads/master@{#437394} |