Skip to content

There should be a way to tell the exact compiler version. #184

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

Closed
kennytm opened this issue Jul 21, 2017 · 8 comments
Closed

There should be a way to tell the exact compiler version. #184

kennytm opened this issue Jul 21, 2017 · 8 comments
Labels
enhancement Something new the playground could do help wanted Not immediately going to be prioritized — ask for mentoring instructions!

Comments

@kennytm
Copy link
Member

kennytm commented Jul 21, 2017

Expose rustc -vV, which can tell you Stable is 1.19.0, Beta is 1.20.0-beta.1, Nightly is 1.20.0-nightly (ae98ebfcb 2017-07-20).

Currently these can only be retrieved by triggering an ICE, which is very inconvenient.

@shepmaster
Copy link
Member

only be retrieved by triggering an ICE

fn main() {
    println!("{:?}", std::process::Command::new("rustc").arg("-vV").output());
}

@shepmaster shepmaster added enhancement Something new the playground could do help wanted Not immediately going to be prioritized — ask for mentoring instructions! labels Jul 21, 2017
@shepmaster shepmaster changed the title Feature request: There should be a way to tell the exact compiler version. There should be a way to tell the exact compiler version. Jul 21, 2017
@kennytm
Copy link
Member Author

kennytm commented Jul 21, 2017

@shepmaster thanks. Still inconvenient 😝

@shepmaster
Copy link
Member

Yep. Do you have a vision of how this information would be presented? I'd like to also eventually show the available crates and their versions, so this type of metadata might want a bit of a home.

@kennytm
Copy link
Member Author

kennytm commented Jul 26, 2017

Adding a "Versions" button to show the versions of the current toolset should be good enough.

screenshot_2017-07-26 23 28 52_81jcma-fs8

@shepmaster
Copy link
Member

Massive props for the thorough mockup! Also, I'm glad you included the clippy / rustfmt versions — I had completely forgotten about them.

I like the idea of having a link to the crate - were you thinking that would go to the crates.io page or somewhere else?

Adding a "Versions" button to show the versions of the current toolset should be good enough.

I'm very hesitant to add more buttons to the current header. They are already so many that a reasonable-sized window cuts them off. Simply wrapping doesn't really help because then the main reason you are on the page (the editor and output fields) get even less space.

I've got some back-of-mind ideas that I'm mulling about. Maybe other people will chime in with some ideas.

@kennytm
Copy link
Member Author

kennytm commented Jul 26, 2017

were you thinking that would go to the crates.io page or somewhere else?

I prefer docs.rs

@shepmaster
Copy link
Member

#219 introduces a bare-bones solution:

image

@shepmaster
Copy link
Member

Ok, the changes in #299 give a place for these:

image

I've opened #300 and #301 for the related parts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Something new the playground could do help wanted Not immediately going to be prioritized — ask for mentoring instructions!
Projects
None yet
Development

No branches or pull requests

2 participants