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

Update Rust #175

Open
lidavidm opened this issue Dec 7, 2018 · 3 comments
Open

Update Rust #175

lidavidm opened this issue Dec 7, 2018 · 3 comments
Assignees

Comments

@lidavidm
Copy link
Contributor

lidavidm commented Dec 7, 2018

No description provided.

@lidavidm lidavidm self-assigned this Dec 7, 2018
@Janzert
Copy link
Contributor

Janzert commented Dec 9, 2018

The two questions I always when updating a language during the contest. Will this effect already submitted bots? And how will this effect users already using the language?

I think rust is probably safe on the first question, as I don't believe it has a runtime that the update would effect. Will this end up changing a dynamically linked standard library though?

I'm not familiar with rust's backward compatibility stance. If a user uploads after the update while having been developing with the current version how likely is that to cause a problem?

@lidavidm
Copy link
Contributor Author

lidavidm commented Dec 9, 2018

Generally Rust will statically link other Rust libraries, including the standard library, since there's not yet a defined ABI. And Rust generally tries to maintain backwards compatibility, though IIRC minor things have broken in the past. They are introducing breaking changes in the latest compiler, but authors have to opt-in to them at the project level.

I could go through the current Rust bots and make sure they still compile and run after the update (there seem to be about 50 currently)

@Janzert
Copy link
Contributor

Janzert commented Dec 10, 2018

I don't think you need to bother checking that they will all still compile without any change. From what you said it sounds like it should be good and if something does break there it will be immediately obvious when the person resubmits.

It also sounds pretty safe that the already compiled bots will continue running without a problem after the upgrade. I would be more inclined to try running those current binaries on an upgraded server or at least keeping a close eye on them right after the upgrade.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants