Johan

Just make a serializable java class that matches the c++ class and use an instance of it to call the RPC?

How about: ```javascript const ifNotNull = f => a => a && f(a) collidesHow(entityA, entityB) |> ifNotNull(onCollision) ``` Not sure what it does to performance but since `ifNotNull(onCollision)` has to...

True, I didn't think of short-circuiting... Still it could be a less ideal but ok workaround I think when the minimal proposal without optional chaining was accepted.

I read about the performance considerations only recently, from the HISTORY.md document. Maybe I missed it, but if this is such a big issue for 4 years already I wonder...

@js-choi Thanks for trying to emphasize with the people on the F# side even when you are on the hack side. As always which such polarizing issues, people almost never...

> I think F#’s conventions about point-free style are excellent: Point-free style is wonderful but should be used judiciously. > > My own belief is that the pipe operator should...

> This does not mean that transplanting F# semantics (which fit with language auto-currying) is a good fit for JavaScript the _language_ (which can never become auto-curried due to backwards...

> Why would I not let the router decide when to debounce? > > 1. opaque payload may make it impossible > 2. the router would need to store extra...

About the stickyness: I think this should be determined by the callee, not by the caller. (So during RPC registration.) Shared registration is also determined by the callee. And stickyness...

Hi, I stumbled upon this thread and the one on google groups about this features and just wanted do dump my thoughts about this feature. In particular about the partitioned...