Skip to content
This repository has been archived by the owner on Apr 13, 2023. It is now read-only.

Modularisation and effect type #155

Open
voidcontext opened this issue Sep 22, 2019 · 2 comments
Open

Modularisation and effect type #155

voidcontext opened this issue Sep 22, 2019 · 2 comments

Comments

@voidcontext
Copy link

Hello,

Is there any chance that this project at some point will support different client backends via modularisation and to be generalised over the effect type (e.g. cats-effect instead of Future, etc...).

@voidcontext voidcontext changed the title Modularisation and effect typeclasses Modularisation and effect type Sep 22, 2019
@Synesso
Copy link
Owner

Synesso commented Sep 23, 2019

For sure, this is needed. A related objective is on the roadmap, but not until Q2 2020. It can be much sooner with contributions, of course. I'll use this issue to define an implementation plan.

@github-actions
Copy link

Stale issue message

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants