John McClean
John McClean
Hey Sean, Most of these integrations were in place for cyclops-react 2 (under separate cyclops versioning of 9). In Cyclops 10 Rx2 and Reactor were promoted to core modules and...
Thanks @Trimax. Which version of cyclops does this bug occur on? (It is not present in the latest cyclops-react, but I would guess cyclops-try may have it?). Thanks again!
Should build on cyclops-reactor to get Lazy collection support.
Yeah that works, IntelliJ will pick up the class files generated via the Gradle build, and oddly enough you can even change those classes one at a time and incremental...
Yeah that would also work, what I mean though is it doesn't help IntelliJ do the compilation itself. It can read the class files generated by javac called via Gradle.
Ah, sorry - I see what you mean now. I was running clean compile. Let me give that a try..
Hey guys - I know this issue is closed, but it seems the best place to pose these questions. I've been playing around with making this work with 3rd party...
It looks like you can create your own Alias's as long as they defined in the same package as __, __2 etc. But a less 'hacky' way for client libraries...
True. You can't recover it directly. ListX (and all the extended collections) might be a special case though because they are wrappers / boxes themselves. They all wrap a collection...
^^^ How I spent my halloween weekend by the way :)