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

Ruby support #300

Open
22 of 23 tasks
ahumenberger opened this issue Jul 31, 2024 · 3 comments
Open
22 of 23 tasks

Ruby support #300

ahumenberger opened this issue Jul 31, 2024 · 3 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@ahumenberger
Copy link
Contributor

ahumenberger commented Jul 31, 2024

We want to add language support for Ruby.

  • Install Ruby in Docker containers
  • Introduce Ruby as a new language
  • Register the Ruby language Finalize Ruby support #327
  • Implement the ExecuteTests method in the Ruby language Finalize Ruby support #327
  • Implement write-tests task
    • Create "plain" repository for Ruby
    • Translate the light repository using a LLM
    • Support Ruby in symflower test
  • Implement code_repair task
    • Translate the mistakes repository using a LLM
    • Implement the Mistakes method in the Ruby language
    • Add missing tests Finalize Ruby support #327
  • Implement transpile task
    • The transpile repository used examples from the light repository, so no need to translate them again
    • Change the way we get the origin/destination languages for transpilation
      • The transpile package names must be e.g. for Go transpile-java, transpile-ruby, instead of just transpile so it is clear which language we are transpiling from
    • Add missing tests Finalize Ruby support #327
  • Documentation
  • Merge fixes Finalize Ruby support #327

Follow-up

@ahumenberger ahumenberger added the enhancement New feature or request label Jul 31, 2024
@ahumenberger ahumenberger added this to the v0.7.0 milestone Jul 31, 2024
@bauersimon
Copy link
Member

For new transpilation tasks, there needs to be some small changes to how the eval figures out which languages are targeted.
Cause right now if we have Go as transpilation source, it automatically assumes Java must be the target cause no other language existed yet.

Munsio added a commit that referenced this issue Aug 1, 2024
ruiAzevedo19 added a commit that referenced this issue Aug 2, 2024
… a language into a helper, for reusability

Part of #300
ruiAzevedo19 added a commit that referenced this issue Aug 2, 2024
ruiAzevedo19 added a commit that referenced this issue Aug 2, 2024
ruiAzevedo19 added a commit that referenced this issue Aug 2, 2024
@ruiAzevedo19 ruiAzevedo19 self-assigned this Aug 2, 2024
ruiAzevedo19 added a commit that referenced this issue Aug 2, 2024
… a language into a helper, for reusability

Part of #300
ruiAzevedo19 added a commit that referenced this issue Aug 2, 2024
ruiAzevedo19 added a commit that referenced this issue Aug 2, 2024
ruiAzevedo19 added a commit that referenced this issue Aug 2, 2024
ruiAzevedo19 added a commit that referenced this issue Aug 5, 2024
ruiAzevedo19 added a commit that referenced this issue Aug 5, 2024
ruiAzevedo19 added a commit that referenced this issue Aug 5, 2024
ruiAzevedo19 added a commit that referenced this issue Aug 5, 2024
ruiAzevedo19 added a commit that referenced this issue Aug 5, 2024
ruiAzevedo19 added a commit that referenced this issue Aug 6, 2024
ruiAzevedo19 added a commit that referenced this issue Aug 6, 2024
ruiAzevedo19 added a commit that referenced this issue Aug 6, 2024
ruiAzevedo19 added a commit that referenced this issue Aug 6, 2024
ruiAzevedo19 added a commit that referenced this issue Aug 6, 2024
…ing from can be infered by the folder name

Part of #300
ruiAzevedo19 added a commit that referenced this issue Aug 6, 2024
…itory, so it can check the new folder structure

Part of #300
bauersimon pushed a commit that referenced this issue Sep 5, 2024
bauersimon added a commit that referenced this issue Sep 5, 2024
bauersimon added a commit that referenced this issue Sep 5, 2024
…ed for coverage tracking when manually executing the examples

Should not matter for within the eval because we always inject that statement anyways.

Part of #300
bauersimon added a commit that referenced this issue Sep 5, 2024
…tom ruby testing init file when verifying folders

Part of #300
bauersimon pushed a commit that referenced this issue Sep 5, 2024
bauersimon added a commit that referenced this issue Sep 5, 2024
bauersimon added a commit that referenced this issue Sep 5, 2024
…ed for coverage tracking when manually executing the examples

Should not matter for within the eval because we always inject that statement anyways.

Part of #300
bauersimon added a commit that referenced this issue Sep 5, 2024
…tom ruby testing init file when verifying folders

Part of #300
bauersimon pushed a commit that referenced this issue Sep 5, 2024
bauersimon added a commit that referenced this issue Sep 5, 2024
bauersimon added a commit that referenced this issue Sep 5, 2024
…ed for coverage tracking when manually executing the examples

Should not matter for within the eval because we always inject that statement anyways.

Part of #300
bauersimon added a commit that referenced this issue Sep 5, 2024
…ause the model is expected to build the absolute path

Part of #300
bauersimon added a commit that referenced this issue Sep 5, 2024
…tom ruby testing init file when verifying folders

Part of #300
bauersimon pushed a commit that referenced this issue Sep 5, 2024
bauersimon added a commit that referenced this issue Sep 5, 2024
bauersimon added a commit that referenced this issue Sep 5, 2024
…ed for coverage tracking when manually executing the examples

Should not matter for within the eval because we always inject that statement anyways.

Part of #300
bauersimon added a commit that referenced this issue Sep 5, 2024
…tom ruby testing init file when verifying folders

Part of #300
bauersimon pushed a commit that referenced this issue Sep 5, 2024
bauersimon added a commit that referenced this issue Sep 5, 2024
bauersimon added a commit that referenced this issue Sep 5, 2024
…ed for coverage tracking when manually executing the examples

Should not matter for within the eval because we always inject that statement anyways.

Part of #300
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants