-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
C# API #124
Comments
It sounds possible, but personally I would try very hard to fit support for Alt and Ch in - they've ended up at the core of things nearly every time I've used Hopac. |
Here is a bit of general discussion on the concepts. I expect most here are already familiar with what I say here. Hopac With C# tasks a call of a function that returns a So, both You mentioned getting fed up with C# tasks. Can you tell more? Personally I find that the C# task model can be trickier to program with due to the way a function call effectively immediately starts a new logical thread. If you don't want to immediately start a new logical thread, you have to carefully manage the point at which the function call is made. |
I'm thinking of creating a limited API mainly around
Job<T>
andPromise<T>
, trying to ignore other concepts as much as possible.Monadic/applicative sugar with LINQ.
Also implement
GetAwaiter
to enable async/await syntax.The rest would be mostly sugar around calling convention (e.g. uncurry functions etc)
I've not actually used Hopac personally so I'm not sure if this limited API is even viable. Do you think that would give a usable API ?
BTW this could probably be just a contrib project on a separate repo, no need to complicate the core repo :)
The text was updated successfully, but these errors were encountered: