| commit | 7411ddb2d716c31f07035ef2aa14c2478e2bb117 | [log] [tgz] |
|---|---|---|
| author | Paul Berry <paulberry@google.com> | Mon Apr 28 13:25:40 2025 -0700 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Apr 28 13:25:40 2025 -0700 |
| tree | e33985597ccdb52aa3f677b6d7ce6986e29c74c8 | |
| parent | cf717accfbe12626587c2476cbdbe9ca0b01a82f [diff] |
[analysis server] Improve dead code removal to prepare for sound-flow-analysis. The following improvements are made to the "remove dead code" quick fix: - Dead code removal can now replace conditional expressions like `condition ? live : dead` or `condition ? dead : live` with just the live subexpression, provided that the condition appears free of side effects. - Dead code removal can now replace `if` statements like `if (condition) live; else dead;` or `if (condition) dead; else live;` with just the live statement, provided that the condition appears free of side effects. - Dead code removal can now fully remove `if` statements like `if (condition) dead;`, provided that the condition appears free of side effects. Extra care is taken around opening and closing braces to try to preserve reasonable formatting as much as possible. These features were chosen by examining the set of new dead code warnings that pop up inside google3 if the sound-flow-analysis language feature is enabled. They are sufficient to allow 98% of those new warnings to be addressed by the quick fix. This should help customers adjust their code quickly when moving to a language version that enables this language feature. The notion that a condition "appears free of side effects" is defined to include casts, non-null assertions, and getter invocations. It is of course possible that a getter invocation, a cast, or a non-null assertion could have a side effect that is important, but it would be difficult to build the necessary static analysis to detect these cases, and in practice, they don't happen very often. Considering that the "remove dead code" quick fix is not usable in an automated fashion (it must be explicitly requested by the user in their editor for each piece of affected dead code), I believe this is a good tradeoff. Bug: https://github.com/dart-lang/sdk/issues/60438 Change-Id: Ied43500c4b7a729bbd686708ab10e80e72f22088 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/425180 Commit-Queue: Paul Berry <paulberry@google.com> Reviewed-by: Samuel Rawlins <srawlins@google.com>
Dart is:
Approachable: Develop with a strongly typed programming language that is consistent, concise, and offers modern language features like null safety and patterns.
Portable: Compile to ARM, x64, or RISC-V machine code for mobile, desktop, and backend. Compile to JavaScript or WebAssembly for the web.
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app. Diagnose app issues using DevTools.
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 in our repo at docs.
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.
Future plans for Dart are included in the combined Dart and Flutter roadmap on the Flutter wiki.