Morgan :)
Morgan :)
Following the internal discussion. We're not blocked, but I think there was some interest in removing it anyway.
``` var parser = ArgParser()..addMultiOption('foo'); parser.parse([])['foo']).add('leaked state'); expect(parser.parse([])['foo'], isEmpty); Expected: empty Actual: ['leaked state'] ``` We could either make the default const or make it always a new copy.
Looking at this code ``` Future waitFor(FutureOr Function() condition, {matcher, Duration timeout = defaultTimeout, Duration interval = defaultInterval}) => clock.waitFor(condition, matcher: matcher, timeout: timeout, interval: interval); ``` I think it...
If you decode a tar file like this: ``` import 'dart:io'; import 'package:archive/archive.dart'; import 'package:archive/archive_io.dart'; void main(args) { if (args.length != 2) { print('usage: example.dart a.tar folder'); return; } String...
New test language/macros/nesting/macro_impl_uses_macro1_test [added here](https://dart-review.googlesource.com/c/sdk/+/352522) has a macro implementation that relies an a macro application, currently it fails on the analyzer. It's possible the fault is not in the analyzer,...
New test language/macros/nesting/macro_impl_uses_macro1_test [added here](https://dart-review.googlesource.com/c/sdk/+/352522) has a macro implementation that relies an a macro application, currently it fails on the CFE. (cfe-strong-linux / cfe-weak-linux) Not sure what's going on here...
Per the spec, macros are not allowed to be used in the same library they are defined, or in the same library cycle. So, the analyzer should report an error....
Per the spec, macros are not allowed to be used in the same library they are defined, or in the same library cycle. So, the CFE should report an error....
**Describe the bug** Calling `Provider.of` when not mounted triggers a codepath that attempts to throw an error but throws a less good error instead; here: ``` if (inheritedElement == null...
Re: [the spec](https://github.com/dart-lang/language/blob/main/working/macros/feature-specification.md#macro-arguments) and [this comment](https://dart-review.googlesource.com/c/sdk/+/341483/comment/01feeabe_1c9d9685/). Macro args have the limitation that they must be serializable, and as currently specified this forces them to be trivially mappable to JSON, i.e....