commit | db07eef77d537bafe05a8546860dcc0e64ef4d3d | [log] [tgz] |
---|---|---|
author | Sam Rawlins <srawlins@google.com> | Wed Oct 27 01:43:21 2021 +0000 |
committer | commit-bot@chromium.org <commit-bot@chromium.org> | Wed Oct 27 01:43:21 2021 +0000 |
tree | 38cd1151a3865ddffdd8e9d37416fe28e981ba9a | |
parent | c46baff9c9a7d10b55d9039f0c75c11ecc41c32a [diff] |
analyzer: visit local variables in resolution more safely I'm preparing for the situation where an expression of (almost) any kind could be wrapped with a generic function instantiation, and I was very worried that there were a lot of cases like this: var localVariable = node.childNode; localVariable.accept(_resolver); // Do more with localVariable. This is dangerous because localVariable may no longer be the same node as `node.childNode`. I searched eerywhere I could for dangerous cases like this. In some cases, I follow the middle statement with `localVariable = node.childNode`, which is a common practice. In other cases, the local variable was only referenced 2 or 3 times, and was unnecessary. In other cases, I saw that the node strictly referred to statements or other types of nodes, like a CatchClause. I am reassured though that there really wasn't too much code like this. I'd love to figure out how to enforce this statically, but haven't found a good solution. Change-Id: If38124dc2036b6f04879a065d66bf3ea73e68977 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/218184 Reviewed-by: Brian Wilkerson <brianwilkerson@google.com> Reviewed-by: Konstantin Shcheglov <scheglov@google.com> Commit-Queue: Samuel Rawlins <srawlins@google.com>
Dart is:
Optimized for UI: Develop with a programming language specialized around the needs of user interface creation.
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app.
Fast on all platforms: Compile to ARM & x64 machine code for mobile, desktop, and backend. Or compile to JavaScript for the web.
Dart's flexible compiler technology lets you run Dart code in different ways, depending on your target platform and goals:
Dart Native: For programs targeting devices (mobile, desktop, server, and more), Dart Native includes both a Dart VM with JIT (just-in-time) compilation and an AOT (ahead-of-time) compiler for producing machine code.
Dart Web: For programs targeting the web, Dart Web includes both a development time compiler (dartdevc) and a production time compiler (dart2js).
Dart is free and open source.
See LICENSE and PATENT_GRANT.
Visit dart.dev to learn more about the language, tools, and to find codelabs.
Browse pub.dev for more packages and libraries contributed by the community and the Dart team.
Our API reference documentation is published at api.dart.dev, based on the stable release. (We also publish docs from our beta and dev channels, as well as from the primary development branch).
If you want to build Dart yourself, here is a guide to getting the source, preparing your machine to build the SDK, and building.
There are more documents on our wiki.
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.