Skip to content

Clarify paper "Destructing Path Function Products" #849

@bvssvni

Description

@bvssvni

I am not sure how to interpret this paper:

  • It could be an early draft for introducing path function product notation for asymmetric paths
  • It could be a way of generalizing path function product notation to automatically duplicate argument when types are dis-ambiguous that this is the case
  • It could be an attempt of explaining a possibility that follows from construction functions through composition

What complicates this further: I seem to remember that the development of Poi influenced which rules should be allowed. Something about two possible interpretations where the first one turned out to be inconsistent. Poi uses the second interpretation and therefore should be used to solve conflicts in papers.

However, Poi does not support path function products yet (not sure it will in the future either). There might be something about path function product notation that allows an interpretation that generalizes to duplication.

Anyway, I am not sure what I meant when writing this paper. Perhaps I can figure it out if other papers references it. Otherwise, I think it can be safely discarded, since I can't remember using this directly.

It could also be the case that notation needs a revisit/cleanup to include updates from experience with Poi.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions