Remove some SVG types from bindings map Our maps are string-based and assume there's only one one @Native class with a given name. This isn't true for these four classes, where there are two types with the same name for each one. This then results in us dropping the definition of one of the two types. Since one of the two types is essentially unused, we should choose to drop that one instead for now. Long-term, we should deprecate the unused types or change our conformance handling to handle multiple types with the same name. We could also choose to unify both definitions, but this may lead to either false positives or renames of members being dropped. This allows us to catch uses of the types that are actually used. Change-Id: I9386cad5b014bee60cd72d21cdf0546640138704 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/341331 Reviewed-by: Sigmund Cherem <sigmund@google.com> Commit-Queue: Srujan Gaddam <srujzs@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.