Tim Whiting comments

Results 455 comments of


                                            Tim Whiting

Exhaustiveness checking on absent map keys

> If we say that a pattern like `{'x': _}` _only_ matches maps of length 1, and you have to write `...` to allow unknown keys, I worry that people...

[records] parse errors when trying to annotate a record type class field

I prefer the more concise syntax for records types. I agree with @lrhn that already `Function` is a bit verbose. Compare: ```dart Record(String, String) doSomething(Record(String, String) Function(Record(int, int), String Function(int))...

[records] parse errors when trying to annotate a record type class field

As another consideration. Right now the Records feature does not break user written classes named `Record` because the user written declaration shadows the dart:core Record, and the record type does...

[records] parse errors when trying to annotate a record type class field

I can't think of any true ambiguity (like you say the following `(` disambiguates like `Function`) but there will be a lot during editing. Here are a few I can...

The docs for riverpod aren't really ready for it to replace provider

> Regarding the toggle: What does composition mean in this context? Hooks? (I am aware of the term composition from the OOP days). And if so, that would be very...

The docs for riverpod aren't really ready for it to replace provider

I'm happy to help with converting any code to code that uses hooks. For the most part it is the same except for the naming of the consumer widgets. Right...

Support query mutation

As a side note, the linter is too aggressive about read vs watch in provider definitions when you are using `FutureProvider` for mutations. (you don't always want to rerun a...

Am I allowed to `ref.watch` in a `FutureProvider` across async gap?

Yes, it is supported, note that the provider will only rebuild when `aProvider` changes until the await completes successfully, at which point `cProvider` is watched, after which the provider will...

Add `@useResult` to copyWith

Great idea, I'm sure it would be a welcome contribution

feat: add common properties with different nullability to base mixin

I don't think this closes #715 which is requesting for a common base class, whereas this just addresses the nullability aspect. This is a great first step though!