- 20 4月, 2021 19 次提交
-
-
由 Oli Scherer 提交于
-
由 Oli Scherer 提交于
-
由 Oli Scherer 提交于
-
由 bors 提交于
coverage of async function bodies should match non-async This fixes some missing coverage within async function bodies. Commit 1 demonstrates the problem in the fixed issue, and commit 2 corrects it. Fixes: #83985
-
由 bors 提交于
Add stability tags to ImportItem. Fixes #83832.
-
由 bors 提交于
Add coverage to continue statements `continue` statements were missing coverage. This was particularly noticeable in a match pattern that contained only a `continue` statement, leaving the branch appear uncounted. This PR addresses the problem and adds tests to prove it. r? `@tmandry` cc: `@wesleywiser`
-
由 bors 提交于
fix few typos in comments
-
由 bors 提交于
Rollup of 7 pull requests Successful merges: - #84123 (Introduce CompileMonoItem DepNode) - #84126 (Enable sanitizers for x86_64-unknown-linux-musl) - #84168 (Lower async fn in traits.) - #84256 (doc: use U+2212 for minus sign in floating-point -0.0 remarks) - #84291 (fix aliasing violations in thread_local_const_init) - #84313 (fix suggestion for unsized function parameters) - #84330 (Remove unused footer section) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
-
由 Dylan DPC 提交于
Remove unused footer section I realized yesterday while working on docs.rs that rustdoc was generating a "footer"section that it doesn't use. No need to keep it then. r? `@jyn514`
-
由 Dylan DPC 提交于
fix suggestion for unsized function parameters taken from `@fasterthanlime's` article https://fasterthanli.me/articles/whats-in-the-box
-
由 Dylan DPC 提交于
fix aliasing violations in thread_local_const_init Fixes https://github.com/rust-lang/rust/pull/83416#discussion_r615364774 r? `@alexcrichton` `@sfackler`
-
由 Dylan DPC 提交于
doc: use U+2212 for minus sign in floating-point -0.0 remarks Also remove plus sign in `-0.0 == +0.0` to make it a valid expression.
-
由 Dylan DPC 提交于
Lower async fn in traits. An error is already created by AST validation. Fixes #84149
-
由 Dylan DPC 提交于
Enable sanitizers for x86_64-unknown-linux-musl Those 4 sanitizers get musl target support in LLVM 12 release.
-
由 Dylan DPC 提交于
Introduce CompileMonoItem DepNode This is likely required for allowing efficient hot code swap support in cg_clif's jit mode. My prototype currently requires re-compiling all functions, which is both slow and uses a lot of memory as there is not support for freeing the memory used by replaced functions yet. cc https://github.com/bjorn3/rustc_codegen_cranelift/issues/1087
-
由 Rich Kadel 提交于
-
由 Tor Hovland 提交于
-
由 lcnr 提交于
-
由 bors 提交于
Match against attribute name when validating attributes Extract attribute name once and match it against symbols that are being validated, instead of using `Session::check_name` for each symbol individually. Assume that all validated attributes are used, instead of marking them as such, since the attribute check should be exhaustive.
-
- 19 4月, 2021 14 次提交
-
-
由 klensy 提交于
-
由 bors 提交于
Slightly change wording in doc comment and fix typo in vec/mod.rs Suggested by `@pickfire` in https://github.com/rust-lang/rust/pull/82760
-
由 Guillaume Gomez 提交于
-
由 bors 提交于
rustdoc: Reduce visual weight of attributes. Followup from #83337. As part of that PR, we stopped hiding attributes behind a toggle, because most things have just zero or one attributes. However, this made clear that the current rendering of attributes emphasizes them a lot, which distracts from function signatures. This PR changes their color of attributes to be the same as the toggles, and reduces their font weight. This also removes `#[lang]` from the list of ALLOWED_ATTRIBUTES. This attribute is an implementation detail rather than part of the public-facing documentation. ![image](https://user-images.githubusercontent.com/220205/115131061-cc407d80-9fa9-11eb-9a77-ad3f3217f391.png) Demo at https://hoffman-andrews.com/rust/de-emph-attr/std/string/struct.String.html#method.trim
-
由 bors 提交于
Improve an error message.
-
由 bors 提交于
rustdoc: get rid of CURRENT_DEPTH Fixes #82742
-
由 Trevor Spiteri 提交于
Co-authored-by: NJubilee <46493976+workingjubilee@users.noreply.github.com>
-
由 bors 提交于
Stablize `non-ascii-idents` This is the stablization PR for RFC 2457. Currently this is waiting on fcp in [tracking issue](https://github.com/rust-lang/rust/issues/55467). r? `@Manishearth`
-
由 Rich Kadel 提交于
The body_span was assumed to be in the Span root context, but this was not the case for async function bodies.
-
由 Rich Kadel 提交于
The initial commit demonstrates the issue, but the fix is not yet implemented. Once corrected... Fixes: #83985
-
由 bors 提交于
Add `Unsupported` to `std::io::ErrorKind` I noticed a significant portion of the uses of `ErrorKind::Other` in std is for unsupported operations. The notion that a specific operation is not available on a target (and will thus never succeed) seems semantically distinct enough from just "an unspecified error occurred", which is why I am proposing to add the variant `Unsupported` to `std::io::ErrorKind`. **Implementation**: The following variant will be added to `std::io::ErrorKind`: ```rust /// This operation is unsupported on this platform. Unsupported ``` `std::io::ErrorKind::Unsupported` is an error returned when a given operation is not supported on a platform, and will thus never succeed; there is no way for the software to recover. It will be used instead of `Other` where appropriate, e.g. on wasm for file and network operations. `decode_error_kind` will be updated to decode operating system errors to `Unsupported`: - Unix and VxWorks: `libc::ENOSYS` - Windows: `c::ERROR_CALL_NOT_IMPLEMENTED` - WASI: `wasi::ERRNO_NOSYS` **Stability**: This changes the kind of error returned by some functions on some platforms, which I think is not covered by the stability guarantees of the std? User code could depend on this behavior, expecting `ErrorKind::Other`, however the docs already mention: > Errors that are `Other` now may move to a different or a new `ErrorKind` variant in the future. It is not recommended to match an error against `Other` and to expect any additional characteristics, e.g., a specific `Error::raw_os_error` return value. The most recent variant added to `ErrorKind` was `UnexpectedEof` in `1.6.0` (almost 5 years ago), but `ErrorKind` is marked as `#[non_exhaustive]` and the docs warn about exhaustively matching on it, so adding a new variant per se should not be a breaking change. The variant `Unsupported` itself could be marked as `#[unstable]`, however, because this PR also immediately uses this new variant and changes the errors returned by functions I'm inclined to agree with the others in this thread that the variant should be insta-stabilized.
-
由 teymour-aldridge 提交于
-
由 Rich Kadel 提交于
And make the LocalDecl internal, to avoid needing to declare storage. (For multiple `continue` stateuemtns, it must also be mutable.)
-
由 Tor Hovland 提交于
-
- 18 4月, 2021 7 次提交
-
-
由 bors 提交于
Don't set fast-math for the SIMD operations we set it for previously Instead of `fast-math`. `fast-math` implies things like functions not being able to accept as an argument or return as a result, say, `inf` which made these functions confusingly named or behaving incorrectly, depending on how you interpret it. It seems that the intended behaviour was to set a `afn` flag instead. In doing so we also renamed the intrinsics to say `_approx` so that it is clear these are not precision oriented and the users can act accordingly. Fixes #84268
-
由 bors 提交于
Fix the wrong return value type description of validateResult It's should be boolean not [boolean].
-
由 Rich Kadel 提交于
`continue` statements were missing coverage. This was particularly noticeable in a match pattern that contained only a `continue` statement, leaving the branch appear uncounted. This PR addresses the problem and adds tests to prove it.
-
由 Waffle Lapkin 提交于
-
由 Ralf Jung 提交于
-
由 Tor Hovland 提交于
-
由 Tor Hovland 提交于
-