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

Different naming of classes/methods and opcode arguments #396

Open
volodya-lombrozo opened this issue Dec 29, 2023 · 0 comments
Open

Different naming of classes/methods and opcode arguments #396

volodya-lombrozo opened this issue Dec 29, 2023 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@volodya-lombrozo
Copy link
Member

The problem raised after the #276 implementation.
We started name all classes and methods with j$ prefix, but after, the next problem raised:

seq > @
  tuple
    com/example/B
    .new
      com/example/A 
      .new
        42
      .bar

As you can see, in the code snippet we have com/example/B and com/example/A arguments, however the corresponding classes were transformed to the following structures:

[] > j$B

and

[] > j$A

So, here we have inconsistency in naming which has to be solved

@volodya-lombrozo volodya-lombrozo self-assigned this Dec 29, 2023
@volodya-lombrozo volodya-lombrozo added the bug Something isn't working label Dec 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant