You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.The text was updated successfully, but these errors were encountered: