Skip to content

Make rust {test, run} exit with appropriate code. - #6730

Closed
hjr3 wants to merge 1 commit into
rust-lang:incomingfrom
hjr3:exit_code
Closed

Make rust {test, run} exit with appropriate code.#6730
hjr3 wants to merge 1 commit into
rust-lang:incomingfrom
hjr3:exit_code

Conversation

@hjr3

@hjr3hjr3 commented May 25, 2013

Copy link
Copy Markdown
Contributor

Scripts need to know if the tests pass or the program ran correctly.

Scripts need to know if the tests pass or the program ran correctly.
bors added a commit that referenced this pull request May 25, 2013
Scripts need to know if the tests pass or the program ran correctly.
@borsbors closed this May 25, 2013
flip1995 pushed a commit to flip1995/rust that referenced this pull request Mar 11, 2021
…r=camsteffen
added new lint `owned_to_owned`
Adding new lint `owned_to_owned`
Creating draft PR to have this looked over.
I think this takes all advice I received into account.
I did have to update the `redundant_clone` test to ignore this lint -- I felt that was the safest action.
closes: rust-lang#6715
changelog: added new lint `implicit_clone`
U007D pushed a commit to U007D/rust-mos that referenced this pull request Aug 21, 2026
8802: Keep comments and attrs when extracting struct from enum variant r=Veykril a=DropDemBits
Fixesrust-lang#6730
Still unsure if existing visibilities of fields should be forced to pub (which is what was previously done), or if it's okay to keep it in the extracted struct.
Co-authored-by: DropDemBits <r3usrlnd@gmail.com>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@hjr3@z0w0@bors