Dart Language and Library Newsletters

This directory contains newsletters about the Dart language and some of its core libraries. For more information about the newsletters, see this news post.

  • November 10, 2017
    • Did you know: Constructors (generative, factory, redirecting, ...)
    • Shorter final variables (:=)
  • November 3, 2017
    • Did you know: Chunked conversions
    • Optional positional and named parameters
  • October 27, 2017
  • October 20, 2017
  • October 13, 2017
    • Follow up: Evaluation order
    • Did you know: double.toString*
    • Why even simple language and library changes require so much thought, and why they often take so much time.
  • October 6, 2017
    • Did you know: Static initializers
    • Changing the evaluation order
  • September 29, 2017
    • Did you know: JSON encoding
    • Fixed-size integers
  • September 22, 2017
    • Did you know: Literal strings
    • Void as a type
  • September 15, 2017
    • Did you know: Labels
    • Making async functions start synchronously (instead of immediately returning)
  • September 8, 2017
    • Follow up: call
    • Fuzzy arrow
    • Enhanced type promotion
  • September 1, 2017
    • The case against call
    • Limitations on generic types
  • August 25, 2017
    • Separating mixins from normal classes
    • Corner cases:
      • Inference vs. manual types
      • Function types and covariant generics
  • August 18, 2017
    • Did you know: Trailing commas
    • Function type syntax: Options we considered
  • August 11, 2017
    • Follow ups
      • Void arrow functions
      • Deferred loading
    • Supporting const functions
    • Shadowing core libraries
  • August 4, 2017
    • Active development:
      • Better organization for docs
      • Void as a type
      • Updates to the core libraries
    • Deferred loading
  • July 28, 2017
    • Intro to the newsletters
    • 1.24 language changes: Function types, two void changes
    • The unified front end, and what that means for language changes
    • Active development:
      • Better organization for docs (focusing on docs/language, with docs/language/informal for specs that aren’t yet in the language spec)
      • Resolved part-of
      • Strong-mode clean zones
      • Void as a type
      • Enhanced type promotion
      • Updates to the core libraries