Dart: Breaking change 44039: Fix HttpClient callback argument nullability

[NewsBot]

A new Dart blog post/announcement has been posted!

A mistake was made during migration of dart:io where some callback arguments were not made nullable, even though the function could be called with null. See Make HttpClient's authenticate and authenticateProxy callbacks accept `null` realm. · Issue #44039 · dart-lang/sdk · GitHub Fixing the mistake is breaking, but only to null-safe code, since it only changes the

Get the full details here: https://groups.google.com/a/dartlang.org/d/msg/announce/A2PLmoQ4Grw/Ue9NA_ByBwAJ

[bot]

Corresponding tweet for this thread:

Devtalk (dev_talk)

Share link for this tweet.

[NewsBot]

A new Dart blog post/announcement has been posted!

(If you expect the change to affect your code negatively, please comment on the issue). /L On Tue, Nov 3, 2020 at 12:08 PM Lasse R.H. Nielsen l...@google.com wrote: > A mistake was made during migration of dart:io where some callback > arguments were not made nullable, even though the function

Get the full details here: https://groups.google.com/a/dartlang.org/d/msg/announce/A2PLmoQ4Grw/aFVvkP1yBwAJ

[bot]

Corresponding tweet for this thread:

Devtalk (dev_talk)

Share link for this tweet.