`+syntax` meta

[yegor256]

How about a +syntax meta that would specify the version of EO that the code is written for:

+syntax 0.59.0

The parser will gracefully refuse to compile if its version is older than the one specified.

[yegor256]

@maxonfjvipon @volodya-lombrozo thoughts?

[Daniilmipt]

Hi! Interesting idea. I looked at the eoc repository and explored how it could be used. If we add a new +syntax feature, I think we should control how it’s used. I have a few examples and questions:

1. We use a parser with a specified version from the maven plugin. If an invalid syntax version is set in a .eo file, we should detect it. The first thing that comes to mind is the linter. Since the linter is responsible for code style and correctness, this task seems appropriate for it

2. Should our parser validate the version specified in the +syntax meta? I think not, because we already run the linter. If we add this check to the parser, it may become slow, since it would need to make API calls for each file that contains a +syntax meta

I have a few ideas on how to solve this:

1. We could add an optional flag for the parser or linter to check the syntax version
2. To reduce API calls, we could introduce a local cache for repeated versions. However, this might be a poor approach if there are many different versions

That’s why I prefer the first option

I’m also concerned about parser performance. Parsing all .eo files could take a long time if there are many of them. This is another reason I’m leaning toward making this check optional

@yegor256

[yegor256]

@Daniilmipt you're right, this issue belongs to the lints repository. They should check the version and report an error if it doesn't match with the parser.

[Daniilmipt]

Can you please help me? I tried to do task and get error in ci (https://github.com/objectionary/lints/actions/runs/22043092841/job/63687180854?pr=798):

command:
Run mvn clean verify -PskipTests -Pqulice --errors --batch-mode

returns:
Error: Failed to execute goal com.qulice:qulice-maven-plugin:0.24.2:check (jcabi-qulice-check) on project lints: Failure: There are 22 violations -> [Help 1]

I can't figure out the error, the stack trace is completely incomprehensible.

[Daniilmipt]

https://github.com/objectionary/lints/actions/runs/22043092841/job/63687180854?pr=798

I found error (https://github.com/objectionary/lints/actions/runs/22043092841/job/63687180854?pr=798#step:5:188), but It wasn't obvious at all. Why it's so hard to understand...

[Daniilmipt]

Okey, I defeated CI. I think you can watch mr

I would also discuss checking SemVer. Because there are different patterns and it is unclear what kind of verification is needed here. I'm only comparing [major, minor, patch], I haven't seen any letter versions in the project