Closed mboes closed 6 years ago
To me, it always felt like a temporary name… to which I never found a better replacement (partly because capabilities-via
does sound good, it has a rhythm to it).
I like the Capabilitynamespace. Let me claim that the modules should have name
Capability.Reader`, etc…
I don't have better than capability
. standard-capabilities
could be an alternative. cl
is somewhat terrible, but is a reference to the mtl
, of course.
I don't think I care all that much personally. I'll let you, @mboes and @aherrmann, choose.
Then it will end up being capability
by default, unless something better comes up soon.
I assume
capabilities-via
was a temporary name. It's leaking an implementation detail that, many years in the future or sooner than that even, will be largely immaterial.There is already an (unmaintained) package called
Capabilities
. We could claimcapability
, with the view towards putting all modules currently at top-level under aCapability.*
namespace.