tomberek
tomberek
Context seems to be a monad bundle of (State,Cancel,Timeouts) used by most Go libraries. It would be convenient to use that idiom with goderive.
I have a few components that make grpc calls which are Context powered. The ability to cancel or to have timeouts set via Context is convenient because the rest of...
The case have is something like this: ``` // Note this receiver func (c HasContext) deriveJoin(in
1,2. Fair point, i added that receiver/method just to get the context from somewhere, but I like your suggestion better, because the context is really describing the bind. I find...
Example of how i am currently addressing this. This can cancel the processors, but i'm not sure if the go func's in deriveJoin become orphaned. ``` type DbService interface {...
There are two types of "Context" that may make sense to track: 1) a Context for the entire pipeline, this may include things like DB connections, GRPC connections. This can...
Still using this approach ``` func (context.Context) func A
I am interested in maintaining a library. I've done a little work with template Haskell and derive. Before I do anything like this I'd like to have a conversation about...
I have come up against situations where it would be convenient to have a function like that. A variation can also be used to introduce new objects into the category....
Like `arr` it is a way to introduce things into the category (in this case, objects, not morphisms). For Hask, `()` is a decent terminal object, but `const` can also...