-
Notifications
You must be signed in to change notification settings - Fork 122
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
eoc unphi
produces untestable programs
#3213
Comments
@deemp only |
@deemp thanks for the report, here is a feedback: Problems
I would recommend specifying a clear and succinct bug title that accurately represents the issue at hand. Please fix the bug report in order it to get resolved faster. |
@deemp I believe this should work in EO
|
It should be this "Φ", but otherwise it works.
I get this EO and can successfully test it.
|
@maxonfjvipon, @yegor256, should we wrap data into According to a discussion (link), we should not. If you think we should, why? |
@deemp we decided that we will translate such expression |
@maxonfjvipon I have one more case: Original EO test:
Original
Resulting EO code after
The last one appears to be incorrect and it does not parse successfully as EO program. @yegor256 FYI: this is similar to the example in the original proposal for the Normalizer, so I imagine, it should work? |
@maxonfjvipon I think simply removing the backslash ( |
@fizruk yes, I was wrong. This backslash is generated by "unphier" but one more symbol
|
@fizruk of course if there's an atom with void attribute:
(technically) its
But we don't (and can't) see it at the level of EO. So it's prohibit for atom to have bound attributes at the level of EO grammar |
@fizruk should be fixed in |
@maxonfjvipon, @yegor256
Related to #2940
Problem
I normalized a PHI file, then converted it to a normalized EO file and tried to run tests from the normalized EO file. However, tests failed.
eoc version
0.19.0
Files
bytes-tests-minimal-initial.phi
:bytes-tests-minimal-normalized.phi
:bytes-tests-minimal-normalized.eo
:Run tests
Error
The text was updated successfully, but these errors were encountered: