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

Does Phi.g4 supports XI without dispatch? #2864

Closed
maxonfjvipon opened this issue Feb 6, 2024 · 9 comments · Fixed by #2867
Closed

Does Phi.g4 supports XI without dispatch? #2864

maxonfjvipon opened this issue Feb 6, 2024 · 9 comments · Fixed by #2867
Assignees

Comments

@maxonfjvipon
Copy link
Member

I see here that XI must have at least one dispatch. However, the following EO program uses $ without an attribute:

[] > prints-itself
  assert-that > @
   length.
     as-phi $
   $.greater-than 0

And it is translated into a ϕ-term with XI and without an attribute:

{org ↦ ⟦eolang ↦ ⟦prints-itself ↦ ⟦φ ↦ Φ.org.eolang.as-phi(α0 ↦ ξ).length.gt(α0 ↦ Φ.org.eolang.int(α0 ↦ Φ.org.eolang.bytes(Δ ⤍ 00-00-00-00-00-00-00-00)))⟧, prints-itself-to-console ↦ ⟦x ↦ Φ.org.eolang.int(α0 ↦ Φ.org.eolang.bytes(Δ ⤍ 00-00-00-00-00-00-00-2A)), φ ↦ Φ.org.eolang.io.stdout(α0 ↦ Φ.org.eolang.as-phi(α0 ↦ ξ))⟧, λ ⤍ Package⟧, λ ⤍ Package⟧}

In particular, it has a subterm

Φ.org.eolang.as-phi(α0 ↦ ξ)

Just want to clarify that this is normal and XI can be used without a dispatch.

It seems our Phi.g4 grammar does not support XI without dispatch, let's find out

@0pdd
Copy link

0pdd commented Feb 6, 2024

@maxonfjvipon the puzzle #2866 is still not solved.

@0pdd
Copy link

0pdd commented Feb 13, 2024

@maxonfjvipon the only puzzle #2866 is solved here.

@maxonfjvipon
Copy link
Member Author

maxonfjvipon commented Feb 13, 2024

@yegor256 let's make a new release with tag 0.35.2, it blocks #2873

@yegor256
Copy link
Member

@rultor release, tag is 0.35.2

@rultor
Copy link
Contributor

rultor commented Feb 13, 2024

@rultor release, tag is 0.35.2

@yegor256 OK, I will release it now. Please check the progress here

@rultor
Copy link
Contributor

rultor commented Feb 13, 2024

@rultor release, tag is 0.35.2

@maxonfjvipon @yegor256 Oops, I failed. You can see the full log here (spent 6min)

yegor256 added a commit that referenced this issue Feb 13, 2024
@yegor256
Copy link
Member

@rultor release, tag is 0.35.2

@rultor
Copy link
Contributor

rultor commented Feb 13, 2024

@rultor release, tag is 0.35.2

@yegor256 OK, I will release it now. Please check the progress here

@rultor
Copy link
Contributor

rultor commented Feb 13, 2024

@rultor release, tag is 0.35.2

@yegor256 Done! FYI, the full log is here (took me 13min)

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.

4 participants