| commit | 98ef250d15b5d10ea61de27268f830cb07ca48a2 | [log] [tgz] |
|---|---|---|
| author | eakuefner <eakuefner@chromium.org> | Fri Jan 27 18:24:01 2017 |
| committer | Commit bot <commit-bot@chromium.org> | Fri Jan 27 18:24:01 2017 |
| tree | 6545b6c80f96ab6d253b6a79b2f37b29f891986d | |
| parent | 3c9b30e0cc0d45d6728dec4440585ffd3ac89b2a [diff] |
[StyleGuide] Allow let in JavaScript code In https://codereview.chromium.org/2466263003 we realized that we should think about our strategy for allowing `let` in Catapult. charliea@ proposed three options for moving to allow it: * Allow `let` but don't recommend it * Recommend it for new code, but not for old code * Recommend it for new code and require fixes to old code as it is modified. On the basis that block scoping is a win for developer productivity, it makes sense to recommend `let` in at least some cases, which throws out the first option. Given that requiring fixes to old code will almost certainly annoy people, and the promise of --fix one day working with processors, that seems to leave the second option as the best possible one. BUG=catapult:#2833 Review-Url: https://codereview.chromium.org/2621643003
Catapult is the home for several performance tools that span from gathering, displaying and analyzing performance data. This includes:
These tools were created by Chromium developers for performance analysis, testing, and monitoring of Chrome, but they can also be used for analyzing and monitoring websites, and eventually Android apps.
Please see our contributor's guide