- 29 8月, 2020 2 次提交
- 28 8月, 2020 34 次提交
-
-
由 bors 提交于
Fix FP in `new_ret_no_self`: trigger in trait def instead of impl block Lint in trait def instead of impl block. Fixes: #5435 changelog: none
-
由 bors 提交于
Rollup of 12 pull requests Successful merges: - #75330 (Improve rendering of crate features via doc(cfg)) - #75927 (Use intra-doc links in `core::macros`) - #75941 (Clean up E0761 explanation) - #75943 (Fix potential UB in align_offset doc examples) - #75946 (Error use explicit intra-doc link and fix text) - #75955 (Use intra-doc links in `core::future::future` and `core::num::dec2flt`) - #75967 (Fix typo in `std::hint::black_box` docs) - #75972 (Fix ICE due to carriage return w/ multibyte char) - #75989 (Rename rustdoc/test -> rustdoc/doctest) - #75996 (fix wording in release notes) - #75998 (Add InstrProfilingPlatformFuchsia.c to profiler_builtins) - #76000 (Adds --bless support to test/run-make-fulldeps) Failed merges: r? @ghost
-
由 Pietro Albini 提交于
Adds --bless support to test/run-make-fulldeps The ability to "bless" output for some of these tests is critical to making it practical to adapt tests to unrelated changes. This is needed for new coverage tests, as shown in PR #76004 . r? @tmandry FYI: @wesleywiser
-
由 Pietro Albini 提交于
Add InstrProfilingPlatformFuchsia.c to profiler_builtins All other Platform files included in `llvm-project/compiler-rt` were present, except Fuchsia. Now that there is a functional end-to-end version of `-Zinstrument-coverage`, I need to start building and testing coverage-enabled Rust programs on Fuchsia, and this file is required. r? @tmandry FYI, @wesleywiser
-
由 Pietro Albini 提交于
fix wording in release notes C-like enums are still allowed to impl drop, you just can't cast them to numbers
-
由 Pietro Albini 提交于
Rename rustdoc/test -> rustdoc/doctest This modules contains the implementation of doctests, and not the tests of rustdoc itself. This name is confusing, so let's rename it to doctest for clarity.
-
由 Pietro Albini 提交于
Fix ICE due to carriage return w/ multibyte char Based off of this [commit](https://github.com/kfitch/rust/commit/972560b83f80e1219b5735ff3d751c034115b08e) Fixes #70381 CC: @Dylan-DPC
-
由 Pietro Albini 提交于
Fix typo in `std::hint::black_box` docs
-
由 Pietro Albini 提交于
Use intra-doc links in `core::future::future` and `core::num::dec2flt` Part of #75080. @rustbot modify labels: A-intra-doc-links T-doc
-
由 Pietro Albini 提交于
Error use explicit intra-doc link and fix text Follow up of https://github.com/rust-lang/rust/pull/75629 r? @jyn514
-
由 Pietro Albini 提交于
Fix potential UB in align_offset doc examples Currently it takes a pointer only to the first element in the array, this changes the code to take a pointer to the whole array. miri can't catch this right now because it later calls `x.len()` which re-tags the pointer for the whole array. https://github.com/rust-lang/miri/issues/1526#issuecomment-680897144
-
由 Pietro Albini 提交于
Clean up E0761 explanation r? @Dylan-DPC
-
由 Pietro Albini 提交于
Use intra-doc links in `core::macros` Part of #75080. Also cleaned up some things. @rustbot modify labels: A-intra-doc-links T-doc T-rustdoc
-
由 Pietro Albini 提交于
Improve rendering of crate features via doc(cfg) The current rendering of crate features with `doc(cfg(feature = ".."))` is verbose and unwieldy for users, `doc(cfg(target_feature = ".."))` is special-cased to make it render nicely, and a similar rendering can be applied to `doc(cfg(feature))` to make it easier for users to read. I also added special casing of `all`/`any` cfgs consisting of just `feature`/`target-feature` to remove the repetitive "target/crate feature" prefix. The downside of this current rendering is that there is no distinction between `feature` and `target_feature` in the shorthand display. IMO this is ok, or if anything `target_feature` should have a more verbose shorthand, because `doc(cfg(feature = ".."))` usage is going to vastly outstrip `doc(cfg(target_feature = ".."))` usage in non-stdlib crates when it eventually stabilizes (or even before that given the number of crates using `cfg_attr(docsrs)` like constructs). ## Previously <img width="259" alt="Screenshot 2020-08-09 at 13 32 42" src="https://user-images.githubusercontent.com/81079/89731110-d090c000-da44-11ea-96fa-56adc6339123.png"> <img width="438" alt="image" src="https://user-images.githubusercontent.com/81079/89731116-d7b7ce00-da44-11ea-87c6-022d192d6eca.png"> <img width="765" alt="image" src="https://user-images.githubusercontent.com/81079/89731152-24030e00-da45-11ea-9552-1c270bff2729.png"> <img width="671" alt="image" src="https://user-images.githubusercontent.com/81079/89731158-28c7c200-da45-11ea-8acb-97d8a4ce00eb.png"> ## Now <img width="216" alt="image" src="https://user-images.githubusercontent.com/81079/89731123-e1d9cc80-da44-11ea-82a8-5900bd9448a5.png"> <img width="433" alt="image" src="https://user-images.githubusercontent.com/81079/89731127-e8684400-da44-11ea-9d18-572fd810f19f.png"> <img width="606" alt="image" src="https://user-images.githubusercontent.com/81079/89731162-2feed000-da45-11ea-98d2-8a88c364d903.png"> <img width="669" alt="image" src="https://user-images.githubusercontent.com/81079/89731991-ccb46c00-da4b-11ea-9416-cd20a3193826.png"> cc #43781
-
由 Thibaud 提交于
Co-authored-by: NEduardo Broto <ebroto@tutanota.com>
-
由 Thibaud 提交于
Co-authored-by: NEduardo Broto <ebroto@tutanota.com>
-
由 Thibaud 提交于
Co-authored-by: NEduardo Broto <ebroto@tutanota.com>
-
由 Camelid 提交于
Co-authored-by: NJoshua Nelson <joshua@yottadb.com>
-
由 bors 提交于
Abort when foreign exceptions are caught by catch_unwind Prior to this PR, foreign exceptions were not caught by catch_unwind, and instead passed through invisibly. This represented a painful soundness hole in some libraries ([take_mut](https://github.com/Sgeo/take_mut/blob/master/src/lib.rs#L37)), which relied on `catch_unwind` to handle all possible exit paths from a closure. With this PR, foreign exceptions are now caught by `catch_unwind` and will trigger an abort since catching foreign exceptions is currently UB according to the latest proposals by the FFI unwind project group. cc @rust-lang/wg-ffi-unwind
-
由 bors 提交于
Fix FP in `to_string_in_display` Don't emit a lint when `.to_string()` on anything that is not `self` Fix #5967 changelog: Fix FP in `to_string_in_display` when calling `.to_string()` on anything that is not `self`
-
由 bors 提交于
Disable cancel-outdated-builds for auto-fallible `cancel-outdated-builds` doesn't need to be enabled on fallible jobs, and it's actually making it harder for us to see if https://github.com/rust-lang/rust/issues/71988 is fixed. This adds some temporary code to avoid `auto-fallible` jobs from being cancelled by our tooling. r? @Mark-Simulacrum
-
由 bors 提交于
Improve help popup Fixes #75623. The second commit is just a slight improvement: the help popup won't be created until someone presses "?" or ESC. Not a big improvement in itself but considering the low amount of code required, I think it was worth the shot. r? @jyn514
-
由 Amanieu d'Antras 提交于
-
由 Rich Kadel 提交于
The ability to "bless" output for some of these tests is critical to making it practical to adapt tests to unrelated changes. This is needed for new coverage tests, as shown in PR #75828 (or its derivative).
-
由 Rich Kadel 提交于
All other Platform files included in `llvm-project/compiler-rt` were present, except Fuchsia. Now that there is a functional end-to-end version of `-Zinstrument-coverage`, I need to start building and testing coverage-enabled Rust programs on Fuchsia, and this file is required.
-
由 tinaun 提交于
C-like enums are still allowed to impl drop, you just can't cast them to numbers
-
由 Camelid 提交于
-
由 Camelid 提交于
-
由 Pietro Albini 提交于
-
由 bors 提交于
Point to a move-related span when pointing to closure upvars Fixes #75904 When emitting move/borrow errors, we may point into a closure to indicate why an upvar is used in the closure. However, we use the 'upvar span', which is just an arbitrary usage of the upvar. If the upvar is used in multiple places (e.g. a borrow and a move), we may end up pointing to the borrow. If the overall error is a move error, this can be confusing. This PR tracks the span that caused an upvar to become captured by-value instead of by-ref (assuming that it's not a `move` closure). We use this span instead of the 'upvar' span when we need to point to an upvar usage during borrow checking.
-
由 ThibsG 提交于
-
由 ThibsG 提交于
-
由 ThibsG 提交于
-
由 Aleksey Kladov 提交于
This modules contains the implementation of doctests, and not the tests of rustdoc itself. This name is confusing, so let's rename it to doctest for clarity.
-
- 27 8月, 2020 4 次提交
-
-
由 bors 提交于
[AVR] Replace broken 'avr-unknown-unknown' target with 'avr-unknown-gnu-atmega328' target The `avr-unknown-unknown` target has never worked correctly, always trying to invoke the host linker and failing. It aimed to be a mirror of AVR-GCC's default handling of the `avr-unknown-unknown' triple (assume bare minimum chip features, silently skip linking runtime libraries, etc). This behaviour is broken-by-default as it will cause a miscompiled executable when flashed. This patch improves the AVR builtin target specifications to instead expose only a 'avr-unknown-gnu-atmega328' target. This target system is `gnu`, as it uses the AVR-GCC frontend along with avr-binutils. The target triple ABI is 'atmega328'. In the future, it should be possible to replace the dependency on AVR-GCC and binutils by using the in-progress AVR LLD and compiler-rt support. Perhaps at that point it would make sense to add an 'avr-unknown-unknown-atmega328' target as a better default when implemented. There is no current intention to add in-tree AVR target specifications for other AVR microcontrollers - this one can serve as a reference implementation for other devices via `rustc --print target-spec-json avr-unknown-gnu-atmega328p`. There should be no users of the existing 'avr-unknown-unknown' Rust target as a custom target specification JSON has always been recommended, and the avr-unknown-unknown target could never pass the linking step anyway.
-
由 Ivan Tham 提交于
Co-authored-by: NJoshua Nelson <joshua@yottadb.com>
-
由 Takayuki Nakata 提交于
Don't emit a lint when `.to_string()` on anything that is not `self`
-
由 Guillaume Gomez 提交于
-