You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem with using the name JobResult is that it's difficult for client code to instantiate it with a sensible name. Eg in extendio, we already have the abstraction called TraverseResult so if we try to create a related type we end up with something like:
TraverseResultJobResult
Which doesn't feel right. If we rename JobResult to JobOutput then we can rename the above to be
TraverseResultJobOutput
Which is a vast improvement.
So the worker pool should never use the term Result in it type names as this is such a natural term for the client to use.
The text was updated successfully, but these errors were encountered:
The problem with using the name JobResult is that it's difficult for client code to instantiate it with a sensible name. Eg in extendio, we already have the abstraction called TraverseResult so if we try to create a related type we end up with something like:
TraverseResultJobResult
Which doesn't feel right. If we rename JobResult to JobOutput then we can rename the above to be
TraverseResultJobOutput
Which is a vast improvement.
So the worker pool should never use the term Result in it type names as this is such a natural term for the client to use.
The text was updated successfully, but these errors were encountered: