Tatumizer

Suppose in the body of the extension method I want to call another static method from the same or different extension. Will this work? ```dart extension on List { static...

If `$arguments` are implemented (see #3742) then forwarding might be within reach, we just need an extra annotation and a spread operator. ```dart foo (int a, int b, {int? c,...

Take 2 (trying to put it more coherently) **Spread operator in parameter list** Let r be a record of statically known type. The expression foo(...r) "unwraps" r and puts all...

The idea can still be resurrected by introducing a type `NoneOr` along the lines of `FutureOr`. This was discussed previously, but there was no appetite for this type because no...

Can this proposal be simplified if you defined the category of "sticky properties" (those that can't be modified by the augmentation) as opposed to "non-sticky" (can't find a better word)...

You don't need classes to return "result or error". Here's my attempt at a zero-cost implementation using extension types. Sure, it doesn't *force* you to check for an error (you...

My understanding is that a tuple doesn't create an object on the heap, it allocates on the stack. In terms of allocation/deallocation overhead, 2-tuple is (almost) equivalent to int. Also,...

There's an option to reuse the syntax of conditional expression by adding some decorations, with a different formatting ```dart var x = if { : cond1 ? expr : cond2...

Suppose the formatter somehow acquires the ability to nicely format this expression. This will solve the problem of if- expressions syntax, right? Then your example of if- statement ```dart if...

I think we are chasing not brevity for its own sake, but rather trying to come up with visually recognizable patterns, and those tend to be relatively short. Imagine that...