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

Future idea: migration tool #69

Open
asbates opened this issue Sep 20, 2024 · 1 comment
Open

Future idea: migration tool #69

asbates opened this issue Sep 20, 2024 · 1 comment
Labels
feature New feature long-term Long-term feature

Comments

@asbates
Copy link

asbates commented Sep 20, 2024

One thing to consider for the future is a migration tool to help convert existing R code to vapour.

This came up in a conversation with a coworker who noted it could be challenging to adopt vapour in existing code bases. The example they gave is vapour's use of = instead of <- for assignment. Of course, this could probably be done via a simple find-and-replace. But I think it suggests people could be hesitant to adopt for fear of the (perceived) workload required to translate R to vapour. Having a tool that can handle most of that could help ease the fear.

@JohnCoene JohnCoene added feature New feature long-term Long-term feature labels Sep 22, 2024
@JohnCoene
Copy link
Contributor

Thanks!

We can think of a tool in the long-term, much of the syntax should be easy to translate but the types will not be.

As Vapour aims to be to R what Typescript is to Javascript, another idea is to add roxgen2 tags that declare types, like jsdoc allows.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature long-term Long-term feature
Projects
None yet
Development

No branches or pull requests

2 participants