Naman Goel
Naman Goel
@sebmck I just updated my first comment. How does compositional functions deal with hoisting? `You can just wrap the function in a method call and it expresses the exact same...
> This isn't an intuitive solution to the hoisting problem and whatever solution is going to be an extreme hack. In that case, perhaps decorators aren't a great idea after...
> No, because class methods aren’t function declarations. Fair enough. I still have my reservations, but my intent was only to have a discussion about this.
It's been a very useful discussion. 1. I agree with @sebmck that the feature should not be nuked for one feature. Honestly it _is_ simpler to wrap functions in functions...
my best take so far is this: ``` let d = macro { rule { $id:ident } => { $id } rule { $pattern:destructor = $rhs:expr ;... } => {...
I'm merely trying to import one `libdef` from another. In particular, I've been trying to write Flow types for `@babel/types`, `@babel/core`, etc. Almost all the modules depend on the types...
I don't see a problem with doing it. @jedwatson ?
A hyperclyck provider to support cmd/ctrl + click would be pretty awesome too!
I have one major concern about not having a dispatcher and using RxJs at all. This is not specific to Rx-Flux, and most Flux implementations are ignoring this problem: the...
@BerkeleyTrue Thanks for the heads-up. Should've read the README more carefully. With this in mind, I no longer think a central Dispatcher is important. It could probably be an optional...