| commit | 9c3e1a1459a3d86fb934ae48a7a6086940eaff3f | [log] [tgz] |
|---|---|---|
| author | Robert Nystrom <rnystrom@google.com> | Wed Feb 26 00:14:51 2025 -0800 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Feb 26 00:14:51 2025 -0800 |
| tree | 7c64aaf7c8922ed1a1028ada045e43b1a88968d8 | |
| parent | 13d11b46edc6664e87e9784c7bf4331dfe9a1d1d [diff] |
Remove support for multi-line error messages in static error tests. The static error test format allows an expected error message to contain newlines like: ```dart some bad code; // [cfe] The error message // is two lines long. ``` Here, the expected error is "The error message\nistwo lines long." This has an unfortunate side effect in that if you have a comment immediately after a static error expectation, it will be treated as part of the expected error: ```dart some bad code; // [cfe] Error. // Unrelated comment. ``` This will expect the CFE to report "Error.\nUnrelated comment." I looked at every static error test and there are no intentional uses of multi-line expectations. The only two I found were both bugs. Since this functionality is unused and error-prone, this CL removes it. Error expectations can only be one line. Fix #60137. Change-Id: I7edb1f60a0c87d4160b93810806de49bc8f55b15 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/412185 Auto-Submit: Bob Nystrom <rnystrom@google.com> Reviewed-by: Johnni Winther <johnniwinther@google.com> Commit-Queue: Johnni Winther <johnniwinther@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.