issa marie tseng

Call onData instead. Replace `return onData;` with `onData([{ name: /* … */ }]);`.

almost forgot: smart people call these bijections.

the more i think about this the more unlikely it is. but also, if we drop IE support we could use `WeakMap`s to simplify the class registration quite a bit.

probably what makes the most sense here is to start with the intermediate libraries and then move on to core

this is a bit tricky though with unreduced varying react—variadic arguments are supplied, and it's sort of awkward to have a non-value argument at the end of an arglist of...

i think this is very doable and i want to make it happen. the main issue is that intermediate libraries would still need some kind of weird env injection to...

we have eliminated the latter problem by swallowing the cost of env injection for intermediate libraries. now the intermediate libraries do require a dollar context in order to function. the...

one possible solution is to refactor binding generation to be based on a Managed Varying. this change would also allow wireEvents to not force artifact, but instead autowire once the...

(same problem with stdlib listview right now)

stared at this for a while and couldn't think of a way that was obviously better than how it's done right now.