These are chat archives for 47deg/fetch

5th
Dec 2017
Raúl Raja Martínez
@raulraja
Dec 05 2017 01:02
Java has no way to represent scala higher kinds and some of the methods would need to be made concrete or specialized. Same for the implicit resolution would have to be wrapped in a scala project that exposes concrete types and already resolved instances with signatures compatible in Java. If you plan on going down that rabbit hole we'd welcome such a submodule in Fetch itself
You probably want ListenableFuture<A> as result type from guava, we have instances to go to that and back in Freestyle async so a Fetch in terms of scala.concurrent.Future can just be ~> to guava's ListenableFuturepotentially.
Tom Adams
@tomjadams
Dec 05 2017 06:46
Thanks for the info @raulraja. The async story in Java is pretty ordinary.
We have a lot of code that mixes concurrency with data access, and some of that data access has hand rolled caches. We also have some future need to be able to see the input state of some data into (the equivalent of) a Fetch, and I think the patterns in Fetch would suit this quite well.
We’re also looking at other things like atomix, I don’t know enough yet though about our use case and future use case to be able to make concrete plans though.
Raúl Raja Martínez
@raulraja
Dec 05 2017 16:54
Cool!, as mentioned if you end up building this atop Fetch let us know and we'll help in whatever we can. 😀
Tom Adams
@tomjadams
Dec 05 2017 19:39
👍🏼