Replies: 1 comment 1 reply
-
|
Yes I agree. I don't have a good idea about how to address this issue though. One possibility is to name the capability after the verb that it permits, for example:
This still doesn't completely solve the problem though, because a Do you have any other suggestions? |
Beta Was this translation helpful? Give feedback.
-
|
I suppose another option is to just lean into this "backwardness" and document it. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Because the capabilities are taken as arguments instead of being a part of the return type like in other effect systems, many of the names feel backwards.
For example, taking a
Streamas an argument doesn't mean that you can read from that stream, but rather that you have the ability to send out things to a stream. In other words, aStreamis aSinkand aConsumeis aSourceinconduitterminology. I guess "having the capability to consume" works in this case though. Another example isException(which also has the issue of a name clash), which is very much not an exception, but rather, the capability toThrowexceptions.I think a good template to try to follow would be such that it fits "the capability to TypeName" as well as possible.
Beta Was this translation helpful? Give feedback.
All reactions