We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm doing this:
$ cat bar.phi {⟦ m ↦ ⟦ x ↦ ⟦ t ↦ 42 ⟧.t ⟧.x ⟧} /code/tmp/eo$ eo-phi-normalizer rewrite bar.phi Rule set following Nov 2024 revision Input: { ⟦ m ↦ ⟦ x ↦ ⟦ t ↦ 42 ⟧ .t ⟧ .x ⟧ } ==================================================== Result 1 out of 1: { ⟦ m ↦ Φ.org.eolang.int ( as-bytes ↦ Φ.org.eolang.bytes ( Δ ⤍ 00-00-00-00-00-00-00-2A ) ) ( ρ ↦ ⟦ t ↦ 42 ⟧ ) ( ρ ↦ ⟦ x ↦ Φ.org.eolang.int ( as-bytes ↦ Φ.org.eolang.bytes ( Δ ⤍ 00-00-00-00-00-00-00-2A ) ) ( ρ ↦ ⟦ t ↦ 42 ⟧ ) ⟧ ) ⟧ } ----------------------------------------------------
Why in one place it's Φ.org.eolang.int (...), while in another place it's just 42? Would be better to have it consistent: always use sugar (42).
Φ.org.eolang.int (...)
42
The text was updated successfully, but these errors were encountered:
@deemp please, check
Sorry, something went wrong.
No branches or pull requests
I'm doing this:
Why in one place it's
Φ.org.eolang.int (...)
, while in another place it's just42
? Would be better to have it consistent: always use sugar (42
).The text was updated successfully, but these errors were encountered: