Juraj Kirchheim

Currently they're collated into a hxxMeta arg, which causes unnecessary allocations.

The function sugar was mostly added for Haxe 3, which didn't have arrow functions. For users who want to continue using it (and for migration), it should be supported via...

Function sugar should generate anonymous calls for https://github.com/HaxeFoundation/haxe/issues/9878

It seems like right now subexpressions often have clashing positions with child lists or tag calls as a whole.

Support dynamic spreads.

1

Especially when working with React passing dynamic props is desired, which is quite different from `tink.Anon.merge` that underpins hxx spreads. Syntax would be `{...untyped }`. Have to figure out what...

Extract constant expressions.

1

Subtrees that rely on constants (including inline / final static fields) should be extracted, so that the differ has less work.

If children are a function, it should be roughly treated as complex attribute function

2

```haxe //Given: function list(attr:{items:Array, children:T->Children}) ' {...attr.children(item)} '; //should compile: hxx(' {name} ') ```

Support KeyValueIterator properly

2

Currently `for (key => val in target)` is treated in a way that doesn't leverage `KeyValueIterator`, which sometimes is slower and sometimes doesn't even compile.

Something as described here would be easy to support: https://github.com/HaxeFoundation/haxe/pull/9476#issuecomment-633234380