Lasse R.H. Nielsen

Makes sense. We have a number of "sink-like" classes, including the `ByteConversionSink`. It makes sense that they could all use an easy way to create an instace.

The error doesn't *necessarily* have ti be uncaught, because it's valid behavior for the `async*` method to continue running immediately after synchronously delivering the event. In that case, the `await`...

The web `Date` object doesn't support microseconds. It's implemented using the JavaScript `Date` object which only supports millisecond precision. So, working as well as possible.

With *records* being a thing, we may want to embrace them. We have a number of "indexed" iterable extensions in [`package:collection`](https://pub.dev/documentation/collection/latest/collection/IterableExtension.html) that would otherwise be worthy candidates for inclusion in...

The `Map.keyed` here is mostly redundant with the existing `Iterable get entries`. You can do `for (var MapEntry(:key, :value) in map.entries) ...` with pattern matching. If we can get rid...

A better error message could be > The web platform library 'dart:js' is not available when compiling to native code. or, for the other direction: > The native platform library...

Dart types do not have inherent default values. The default value of the `int` type is not `0`, because there is no default value. Even if `[this.id, this.name]` knows that...

Well, it hasn't so far. It's not *impossible*, but it's also not providing a big value. It wouldn't allow anything you cannot express today, you just have to do it...

The one general rule about imports is to never have any relative path from a file inside `lib` to a file outside of `lib`, or vice versa. (Never have `/lib/`...

This could be a `replace` method on `DateTime`, like the one on `Uri`.