[dart2wasm] Use native int parsing in JSCM JSCM (JS compatibility mode) started as an experiment to have a compilation mode that is semantically as close to dart2js as possible, to make migration from dart2js easy. However we've since decided to follow VM semantics in dart2wasm, and JSCM now mainly exists to test JS-backed typed data and string classes. The default mode allocates Wasm-array-backed strings and typed data classes when they are allocated in Dart, so the JS-backed classes are are only tested in JS interop tests in the default mode. In JSCM we only have JS-backed classes so all tests allocate JS-backed typed data and string classes. Integer parsing in JSCM is currently just a `parseInt` JS call, which is not compatible with the VM or dart2js semantics. Since which one to follow does not make any difference in terms of test coverage of dart2wasm standard library, do the simple thing and reuse the default mode's `int` parser. Fixes these tests in JSCM: - co19/LanguageFeatures/Digit-separators/parse_A01_t01 - co19/LanguageFeatures/Digit-separators/parse_A01_t02 - co19/LanguageFeatures/Digit-separators/parse_A01_t03 - co19/LanguageFeatures/Digit-separators/parse_A03_t01 - co19/LanguageFeatures/Digit-separators/parse_A03_t02 - co19/LanguageFeatures/Digit-separators/parse_A03_t03 - co19/LibTest/core/Uri/parseIPv6Address_A02_t01 - co19/LibTest/core/int/parse_A01_t02 - co19/LibTest/core/int/parse_A02_t01 - co19/LibTest/core/int/parse_A03_t02 - co19/LibTest/core/int/parse_A04_t02 - corelib/int_parse_radix_int64_test/02 - corelib/int_parse_radix_test/02 - corelib/int_parse_radix_test/none - corelib/int_parse_with_limited_ints_test - corelib/int_try_parse_test - corelib/integer_parsed_arith_vm_test - corelib/integer_parsed_div_rem_vm_test/01 - corelib/integer_parsed_div_rem_vm_test/none - corelib/integer_parsed_mul_div_vm_test - corelib/num_parse_test/01 - corelib/num_parse_test/none - corelib/num_try_parse_test - corelib/uri_ipv4_test - corelib/uri_test - language/operator/arithmetic_int64_test - language/operator/arithmetic_test - lib/async/stream_controller_test - lib/convert/json_chunk_test - lib/convert/json_test - lib/convert/json_utf8_chunk_test - lib/math/math2_test - lib/math/math_test Fixes #56849. Change-Id: Iea72eeb39a80e00c023b780c185b4fabe549c568 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/390860 Reviewed-by: Slava Egorov <vegorov@google.com> Commit-Queue: Ömer Ağacan <omersa@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.