Tim Disney
Tim Disney
@vegansk various background tasks have been completed but nothing directly on supporting TS/Flow in sweet. I'm definitely motivated since everything I write now is in flow (even sweet core!). My...
@gabejohnson I haven't looked into it in any depth yet but yeah that would probably be my initial approach.
@slotik no need to open a shift issue. I chatted with them (sorry, forgot to update this thread) and the shift project is uninterested in type annotations in their core...
It's still being developed, just been busy the past few months. Hope to get some time soon.
Yeah right around [here](https://github.com/sweet-js/sweet.js/blob/bcbfa484bc7ee92f975aa050c5b205971e4c2e2c/src/term-expander.js#L550-L580) it looks like the hygiene stuff isn't taking into account initializers. It needs to apply the function scope in initializers. Also, I think the current CloneReducer...
Humm...why doesn't the second and third cases just throw a "failed to match" error?
Yeah, I think I really like this.
@jimmyhmiller I actually don't think there's anything holding this back. In fact I don't think we even need to do this in core since `match` (or something like it) can...
That all sounds great to me. Use all the FP! Your composability goal still comes down to "last write wins" right? Just with a well defined method for doing that...
> I think a trie is the way to go, but I think I'll start with POJOs and linear algorithms first to test out the API. 👍 > I'll get...