https://boringssl.googlesource.com/boringssl.git/+log/f449f7206f62..047c29fe2c3e 2026-06-01 chlily@google.com Documentation: Change |...| to `...` for code references in comments 11/N 2026-06-01 chlily@google.com Documentation: Change |...| to `...` for code references in comments 10/N 2026-06-01 chlily@google.com Documentation: Change |...| to `...` for code references in comments 8/N 2026-06-01 chlily@google.com Documentation: Change |...| to `...` for code references in comments 7/N 2026-06-01 chlily@google.com Documentation: Change |...| to `...` for code references in comments 6/N 2026-06-01 chlily@google.com Documentation: Change |...| to `...` for code references in comments 5/N 2026-06-01 chlily@google.com Documentation: Change |...| to `...` for code references in comments 4/N 2026-06-01 chlily@google.com Documentation: Change |...| to `...` for code references in comments 3/N 2026-06-01 rpolzer@google.com CI/CQ custom libc++: enable bounds checked containers. 2026-06-01 rpolzer@google.com CI/CQ custom libc++: enable unspecified sorting order randomization. 2026-06-01 rpolzer@google.com armv8 assembly: do not branch to global symbols. 2026-06-01 davidben@google.com Rewrite add_cert_dir's directory string parsing 2026-06-01 davidben@google.com Turn SSL_CTX into an opaque struct 2026-05-31 davidben@google.com Test that X509_LOOKUP_hash_dir ignores duplicates 2026-05-31 chlily@google.com Update style guide to change |...| to `...` for code in comments 2026-05-30 chlily@google.com Documentation: Change |...| to `...` for code references in comments 2/N 2026-05-30 chlily@google.com Documentation: Change |...| to `...` for code references in comments 1/N 2026-05-29 davidben@google.com Fix SSL_OP_LEGACY_SERVER_CONNECT with TLS 1.3 2026-05-28 davidben@google.com Add some tests for file and fd BIOs 2026-05-28 rpolzer@google.com Add the proper limit to PKCS5_PBKDF2_HMAC. 2026-05-28 rpolzer@google.com Fix limits for AES-GCM-SIV. 2026-05-28 rpolzer@google.com AES-CTR-HMAC: Apply the 64 GiB limit to open operations too. 2026-05-27 davidben@google.com Release name_list if SSL_set0_client_CAs does nothing 2026-05-27 davidben@google.com Fix OBJ_dup's handling of malloc failures 2026-05-27 davidben@google.com Restore the SSL_OP_LEGACY_SERVER_CONNECT option 2026-05-27 rpolzer@google.com CBB_cleanup: null out the buffer pointer if it was freed. 2026-05-27 rpolzer@google.com Fix uninitialized data read by AES-GCM-SIV assembly. 2026-05-27 rpolzer@google.com EVP_CTRL_GCM_IV_GEN: reject if the IV length is <8. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/boringssl-dart-sdk Please CC dart-engprod@google.com,dart-vm-gardener@rotations.google.com,dart-vm-team@google.com on the revert to ensure that a human is aware of the problem. To file a bug in BoringSSL: https://crbug.com/boringssl/new To file a bug in Dart SDK: https://github.com/dart-lang/sdk/issues To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Tbr: dart-vm-gardener@rotations.google.com Change-Id: Ie5ccbd48411358c59f0894ca5cc2bc2ab4afb936 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/508204 Commit-Queue: Alexander Markov <alexmarkov@google.com> Reviewed-by: Ryan Macnak <rmacnak@google.com> Reviewed-by: Alexander Markov <alexmarkov@google.com>
Dart
An approachable, portable, and productive language for high-quality apps on any platform
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).
License & patents
Dart is free and open source.
See LICENSE and PATENT_GRANT.
Using Dart
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).
Building Dart
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.
Contributing to Dart
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.
Roadmap
Future plans for Dart are included in the combined Dart and Flutter roadmap on the Flutter wiki.