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

Remove meaningless comments in src/test #63411

Closed
wants to merge 190 commits into from
Closed

Remove meaningless comments in src/test #63411

wants to merge 190 commits into from

Conversation

sd234678
Copy link
Contributor

@sd234678 sd234678 commented Aug 9, 2019

Per @Centril's comment on #63347

newpavlov and others added 30 commits July 17, 2019 18:36
* Allow items to be accessible through private modules and fields when a
  macro can access them.
* Don't mark type-private items as reachable.
* Never make items exported/public via macros
They were reachable through opaque macros defined in `core`
Co-Authored-By: Mazdak Farrokhzad <twingoow@gmail.com>
Co-Authored-By: Oliver Middleton <olliemail27@gmail.com>
Merge recent changes into master
bjorn3 and others added 22 commits August 11, 2019 16:51
ty::Instance is small and Copy, we should not be adding additional
indirection.
This update includes the ability to warn on deprecated config keys.
It's important to be able to warn the user whenever they're using
an old configuration rather than giving them a cryptic "unknown
configuration error"

cc rust-lang/vscode-rust#639

Since we removed a config value in the current nightly, it'd be
very good if this change can make also make it before cutting the
next release.
Add #[repr(transparent)] for several types

In some functions, types mentioned in this PR are transmuted into their inner value.
Example for `PathBuf`: https://github.com/rust-lang/rust/blob/master/src/libstd/path.rs#L1132.
This PR adds `#[repr(transparent)]` to those types, so their correct behavior doesn't depend on compiler details. (As far as I understand, currently that line, converting `PathBuf` to `Vec<u8>`, is UB).
Lint on some incorrect uses of mem::zeroed / mem::uninitialized

Cc #62825 and https://internals.rust-lang.org/t/make-mem-uninitialized-and-mem-zeroed-panic-for-some-types-where-0-is-a-niche/10605

This does not yet handle `NonNull`/`NonZero*`, but it is a start.

I also improved some doc issues I hit on the way, and added a useful helper to `TyS`.

EDIT: I added the relnotes label mostly as a proposal -- I think this is worth mentioning, but leave the decision up to the release team.
rename RUST_CTFE_BACKTRACE to RUSTC_CTFE_BACKTRACE

This matches `RUSTC_LOG`. Both affect only rustc, not any Rust program.
Add an example to show how to insert item to a sorted vec

Closes #61684
cc #61742
r? @Mark-Simulacrum, @jonas-schievink
…Gomez

rustdoc: general cleanup

Almost all commits stand alone; but all commits can be reviewed individually.
Copy ty::Instance instead of passing by reference

ty::Instance is small and Copy, we should not be adding additional
indirection.

Fixes #63409.

r? @eddyb
Rollup of 8 pull requests

Successful merges:

 - #61969 (Add #[repr(transparent)] for several types)
 - #63346 (Lint on some incorrect uses of mem::zeroed / mem::uninitialized)
 - #63433 (Miri shouldn't look at types)
 - #63440 (rename RUST_CTFE_BACKTRACE to RUSTC_CTFE_BACKTRACE)
 - #63441 (Derive Debug for CrateInfo)
 - #63442 (Add an example to show how to insert item to a sorted vec)
 - #63453 (rustdoc: general cleanup)
 - #63464 (Copy ty::Instance instead of passing by reference)

Failed merges:

r? @ghost
Update RLS

This update includes the ability to warn on deprecated config keys.
It's important to be able to warn the user whenever they're using
an old configuration rather than giving them a cryptic "unknown
configuration error"

cc rust-lang/vscode-rust#639

Since we removed a config value in the current nightly, it'd be
very good if this change can make also make it before cutting the
next release.
libsyntax: Refactor `parser.rs` into reasonably sized logical units

Here we split `parser.rs` (~7.9 KLOC) into more reasonably sized files (all < 1.8 KLOC):

- `./src/libsyntax/parse/`
   - `parser.rs`
   - `parser/`
      - `pat.rs`
      - `expr.rs`
      - `stmt.rs`
      - `ty.rs`
      - `path.rs`
      - `generics.rs`
      - `item.rs`
      - `module.rs`

Closes #60015.

r? @petrochenkov
@sd234678
Copy link
Contributor Author

Think I might have made a mistake trying to rebase there. Would it be better for me to open a new branch from master and cherry-pick my commits onto that?

@Centril
Copy link
Contributor

Centril commented Aug 12, 2019

@sd234678 Yeah that will probably go faster. ^^

@sd234678
Copy link
Contributor Author

Moved to #63487

@sd234678 sd234678 closed this Aug 12, 2019
@sd234678 sd234678 deleted the remove-meaningless-comments-in-src/test branch August 12, 2019 08:43
Centril added a commit to Centril/rust that referenced this pull request Aug 15, 2019
…s-in-src/test-2, r=Centril

Remove meaningless comments in src/test

Moved from rust-lang#63411
Centril added a commit to Centril/rust that referenced this pull request Aug 17, 2019
…s-in-src/test-2, r=Centril

Remove meaningless comments in src/test

Moved from rust-lang#63411
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-review Status: Awaiting review from the assignee but also interested parties.
Projects
None yet
Development

Successfully merging this pull request may close these issues.