Date: Wed, 28 Aug 2019 13:15:51 +0300
On Wed, 28 Aug 2019 at 07:18, Andrew Tomazos via Lib-Ext
<lib-ext_at_[hidden]> wrote:
>
> I think modelling a path as a container of its components is reasonable.
>
> What isn't reasonable is that those components are themselves paths, as this would imply that the value of a single-component path P is a container of one item, and that one item contained in P has the value P. A container shouldn't be able to contain itself. It's nonsensical.
It's perfectly sensical for hierarchical things, but I'm not entirely
convinced that path components are such things under paths.
> I think what I'm saying is that filesystem paths and filesystem path components should obviously be distinct types.
By that obviousness claim, we should've seen a proposal for that by now.
<lib-ext_at_[hidden]> wrote:
>
> I think modelling a path as a container of its components is reasonable.
>
> What isn't reasonable is that those components are themselves paths, as this would imply that the value of a single-component path P is a container of one item, and that one item contained in P has the value P. A container shouldn't be able to contain itself. It's nonsensical.
It's perfectly sensical for hierarchical things, but I'm not entirely
convinced that path components are such things under paths.
> I think what I'm saying is that filesystem paths and filesystem path components should obviously be distinct types.
By that obviousness claim, we should've seen a proposal for that by now.
Received on 2019-08-28 12:16:06