bjoernager/rust
bjoernager/rust
1
Fork 0
Code Issues Pull requests Activity

Insert some blank lines.

Browse source 
After things that are immediately followed by a `use` declaration and
look like they might apply to that `use` item but actually don't.
This commit is contained in:
Nicholas Nethercote 2024-07-30 07:21:13 +10:00
parent bd24763aaf
commit 70fcf9e790
3 changed files with 4 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
compiler/rustc_lint/src/macro_expr_fragment_specifier_2024_migration.rs
View file

@ -1,5 +1,5 @@
//! Migration code for the `expr_fragment_specifier_2024` //! Migration code for the `expr_fragment_specifier_2024` rule.
//! rule.
use rustc_ast::token::{Token, TokenKind}; use rustc_ast::token::{Token, TokenKind};
use rustc_ast::tokenstream::{TokenStream, TokenTree}; use rustc_ast::tokenstream::{TokenStream, TokenTree};
use rustc_session::lint::FutureIncompatibilityReason; use rustc_session::lint::FutureIncompatibilityReason;

1
library/std/src/sys/pal/sgx/thread.rs
View file

@ -1,4 +1,5 @@
#![cfg_attr(test, allow(dead_code))] // why is this necessary? #![cfg_attr(test, allow(dead_code))] // why is this necessary?
use super::abi::usercalls; use super::abi::usercalls;
use super::unsupported; use super::unsupported;
use crate::ffi::CStr; use crate::ffi::CStr;

1
library/std/src/sys/pal/windows/net.rs
View file

@ -21,6 +21,7 @@ pub mod netc {
//! //!
//! Some Windows API types are not quite what's expected by our cross-platform //! Some Windows API types are not quite what's expected by our cross-platform
//! net code. E.g. naming differences or different pointer types. //! net code. E.g. naming differences or different pointer types.
use core::ffi::{c_char, c_int, c_uint, c_ulong, c_ushort, c_void}; use core::ffi::{c_char, c_int, c_uint, c_ulong, c_ushort, c_void};
use crate::sys::c::{self, ADDRESS_FAMILY, ADDRINFOA, SOCKADDR, SOCKET}; use crate::sys::c::{self, ADDRESS_FAMILY, ADDRINFOA, SOCKADDR, SOCKET};