Skip to content

Non-finite internal branching #3

@YaZko

Description

@YaZko
Contributor

We currently restrict internal branching to finite branching, indexed by Fin types.
This is a clear restriction, and an immediate blocking point in experimental applications investigated by @nchappe.

Two possibilities:

  • Allow for indexation by either a Fin type, or by nat
  • Allow for indexation by an arbitrary type. In this case, the indexes used by a given computation must become a parameter of the datatype, similar to E for external interactions.

Exposing statically the indexes used in the second solution is mandatory if any notion akin to interpretation of internal non-determinism is to be defined in the future (and it shall!).

Activity

self-assigned this
on Feb 12, 2022
YaZko

YaZko commented on Apr 14, 2022

@YaZko
ContributorAuthor

See the branch choice-gen by @nchappe which addresses this issue.

We plan on merging it to master eventually, but probably not before a first 1.0 without it is stable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

    Development

    No branches or pull requests

      Participants

      @YaZko@nchappe

      Issue actions

        Non-finite internal branching · Issue #3 · vellvm/ctrees