Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problems of the Mugda paper #2

Open
xieyuheng opened this issue Oct 22, 2022 · 3 comments
Open

Problems of the Mugda paper #2

xieyuheng opened this issue Oct 22, 2022 · 3 comments

Comments

@xieyuheng
Copy link
Member

xieyuheng commented Oct 22, 2022

(1) Equivalent without type is wrong, because the meaning of equivalent is only determined for specific type.

(2) Ap has target & args instead of target & arg.

(3) Using Var & Ap as Value instead of defining a Neutral type.

@xieyuheng
Copy link
Member Author

xieyuheng commented Oct 22, 2022

(4) No TypedNeutral, no typed directed readback, thus can not handle eta rules.

@xieyuheng
Copy link
Member Author

xieyuheng commented Oct 22, 2022

(5) The meaning of Values.Ap is overloaded.

The paper uses (A):

  • Data
  • Ctor

Maybe we should use (B):

  • Datatype
  • DatatypeCtor -- Data of the paper
  • Data
  • DataCtor -- Ctor of the paper

@xieyuheng
Copy link
Member Author

Pros and Cons about (5):

(A) is gooder:

  • In (A), Exp is close to Value.

(B) is gooder:

  • In (B), doAp will be clear.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant