-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Re-open discussion around mentioning the target #2894
Comments
I believe @jonathandturner is working on a rebase of that PR and will open a new PR shortly |
PR: #2896 |
Closed with #2909 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'd like to reopen the discussion on #1374. We're still seeing new-to-Rust users tripping over this. Specifically, things like this:
https://www.reddit.com/r/rust/comments/4tikmf/why_is_my_forth_virtual_machine_written_in_rust/
Should be almost impossible to happen for new users. Users should be able to easily see the target and get clued in that the unintended target is being built.
@alexcrichton mentions a simple fix by mentioning the target in the build message, and I think this is perfectly fine. We don't need an over-engineered, show-all-the-things approach, but instead just simply write the target name. If we support custom target, we can put that there too.
The key piece, though, is cluing in users at a glance to what's going on.
The text was updated successfully, but these errors were encountered: