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

replace auto-named-attr-at-XX-XX with αX #3674

Closed
yegor256 opened this issue Dec 16, 2024 · 4 comments · Fixed by #3938
Closed

replace auto-named-attr-at-XX-XX with αX #3674

yegor256 opened this issue Dec 16, 2024 · 4 comments · Fixed by #3938
Assignees

Comments

@yegor256
Copy link
Member

Currently, we give names to anonymous objects:

[] > foo
  [] >>
    42 > @

The name given will be: auto-named-attr-at-XX-XX. This is too long. Let's name them α5, α6, etc., where the index is the total count of attributes in the object plus 1.

@yegor256
Copy link
Member Author

@maxonfjvipon please, help

@maxonfjvipon
Copy link
Member

@yegor256 how about that?


[] > foo
  [] >>
    42 > @
  [] >>
    42 > @

Here foo would have two a2 attributes

@yegor256
Copy link
Member Author

@maxonfjvipon obviously, in this case we name them α1 and α2

@maxonfjvipon
Copy link
Member

@yegor256 how to convert such objects to phi?

EO:
[] > foo
  [] >>
    42 > @

OR:
[] > foo
  [] > α1
    42 > @

PHI:
[
  foo -> [
    α1 -> [
      @ -> 42
    ]
  ]
]

Such PHI expression is not valid since we've prohibited bindings with α in formation

maxonfjvipon added a commit to maxonfjvipon/eo that referenced this issue Feb 21, 2025
maxonfjvipon added a commit to maxonfjvipon/eo that referenced this issue Feb 21, 2025
maxonfjvipon added a commit to maxonfjvipon/eo that referenced this issue Feb 21, 2025
maxonfjvipon added a commit to maxonfjvipon/eo that referenced this issue Feb 21, 2025
maxonfjvipon added a commit to maxonfjvipon/eo that referenced this issue Feb 21, 2025
maxonfjvipon added a commit to maxonfjvipon/eo that referenced this issue Feb 21, 2025
github-merge-queue bot pushed a commit that referenced this issue Feb 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants