Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • A Actris
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Iris
  • Actris
  • Merge requests
  • !25

WIP: Interpretation of πDILL

  • Review changes

  • Download
  • Email patches
  • Plain diff
Open Dan Frumin requested to merge dfrumin/actris:ill into master May 10, 2021
  • Overview 1
  • Commits 30
  • Pipelines 0
  • Changes 6

Hi, I would like to request comments on something that I've been working on.

πDILL is a type system based on intuitionistic linear logic, formulated in the dual context-style: https://doi.org/10.1017/S0960129514000218

In this PR I tried to write down the interpretation for this system using heap_lang (instead of pi-calculus), and interpret the types with Actris channels.

Why I thought this might be interesting?

  • I wanted to learn Actris
  • The type system fundamentally requires higher-order channels (something that is well supported in Actris)
  • It shows an example of "non-manifest" sharing, where one endpoint (a "server") is shared among clients, but all the client-server interactions are totally disjoint from each other.

Overview of changes in this PR:

  • Some facts about substitutions; the is_closed_expr_set was taken from ReLoC.
  • A lemma about big_sepM2.
  • In order to implement this "non-manifest sharing" (for the interpretation of ! A types) I had to tweak the iProto_owns definition and formulate a log-atomic style specifications for the send operation.

I think the first two items are orthogonal to Actris/DILL so it might sense to see if those results can be generalized and move upstream.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: ill