Hacker News new | ask | show | jobs
by tobias12345 773 days ago
Nope, editions cover that use case nicely: Rust breaks things every three years -- without breaking existing code.

Basically you have to opt in your project to the new normal. All your projects dependencies can opt in, too, whenever they want to make the jump. Nobody has to opt in though.

Maybe C++ can do something similar eventually once modules are used everywhere. Those have a much cleaner separation of code between individual project parts than you can have with headers.

1 comments

Rust is already at a done/stable stage, and won’t make major changes even if it theoretically could.

Change proposals that cause churn are regularly shot down.