[stable][vm/io] Avoid %ls in SetOsErrorMessage Issue description: Users are getting confusing "Fatal error in Utils::VSNPrint" instead of appropriate error message when using dart. What is the fix: Avoid using %ls format specifier, use explicit WideToUtf8Scope conversion. Why cherry-pick: Avoid confusing "Fatal error" when errors are reported. Risk: Low Issue link: https://github.com/dart-lang/sdk/issues/62252 Original description is below. This format specifier does not perform a wide char to utf8 conversion but rather a locale dependent wide char to multibyte conversion (essentially wcstombs), which is not what this function is expecting to do (it is expected to return utf8 encoded error message). Issue https://github.com/dart-lang/sdk/issues/62252 TEST=not tested, speculative fix Cherry-pick: https://dart-review.googlesource.com/c/sdk/+/468800 Change-Id: I97eda5caed9b7ea5ac29271f7cdf2d77700f6980 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/468842 Reviewed-by: Nate Biggs <natebiggs@google.com> Commit-Queue: Alexander Aprelev <aam@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.