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

Extend grammar to mark objects to be named automatically #3164

Closed
maxonfjvipon opened this issue May 3, 2024 · 3 comments · Fixed by #3165
Closed

Extend grammar to mark objects to be named automatically #3164

maxonfjvipon opened this issue May 3, 2024 · 3 comments · Fixed by #3165
Assignees

Comments

@maxonfjvipon
Copy link
Member

It would be convenient to have a syntax construction in EO which would signal to compiler that object should be named automatically without explicit name from end-user.
For example:

[] > object
  x
    [] >>
      5.plus 5 > ten

Here >> signals that this abstract object should be uniquely named automatically by compiler.
Only abstract objects should be able to use such syntax

@maxonfjvipon maxonfjvipon self-assigned this May 3, 2024
@maxonfjvipon maxonfjvipon changed the title Different behaviour in EO-to-java generation Extend grammar to mark objects to be named automatically May 3, 2024
Copy link

github-actions bot commented May 3, 2024

@maxonfjvipon thanks for the report, here is a feedback:

Problems

  • The bug report title is too generic and doesn't accurately describe the issue. It needs to be brief and informative.
  • Absence of details about the software environment or version where the problem has occurred. This data is crucial for developers to recreate the issue.
  • The bug report does not include steps to replicate the problem, which makes it difficult for developers to comprehend and address the issue.

Suggestion

Improve the bug report title to accurately and concisely describe the issue, for example: "Need for Auto-Naming Syntax in EO Compiler for Abstract Objects".

Please fix the bug report in order it to get resolved faster.
Analyzed with gpt-4

@yegor256
Copy link
Member

yegor256 commented May 3, 2024

@maxonfjvipon if this is only applicable for abstract objects, maybe we can use this syntax (no space after the []):

[] > object
  x
    []>
      5.plus 5 > ten

@maxonfjvipon
Copy link
Member Author

maxonfjvipon commented May 3, 2024

@yegor256 as for me []> looks like syntax error because of the missed space. Let's stick with >> for now. We'll be able to change it anytime in the future when it works

maxonfjvipon added a commit to maxonfjvipon/eo that referenced this issue May 4, 2024
maxonfjvipon added a commit to maxonfjvipon/eo that referenced this issue May 4, 2024
maxonfjvipon added a commit to maxonfjvipon/eo that referenced this issue May 4, 2024
maxonfjvipon added a commit to maxonfjvipon/eo that referenced this issue May 4, 2024
maxonfjvipon added a commit to maxonfjvipon/eo that referenced this issue May 4, 2024
maxonfjvipon added a commit to maxonfjvipon/eo that referenced this issue May 4, 2024
maxonfjvipon added a commit to maxonfjvipon/eo that referenced this issue May 6, 2024
maxonfjvipon added a commit to maxonfjvipon/eo that referenced this issue May 6, 2024
maxonfjvipon added a commit to maxonfjvipon/eo that referenced this issue May 6, 2024
maxonfjvipon added a commit to maxonfjvipon/eo that referenced this issue May 6, 2024
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