Insert some blank lines.
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:
parent
bd24763aaf
commit
70fcf9e790
3 changed files with 4 additions and 2 deletions
|
@ -1,5 +1,5 @@
|
|||
//! Migration code for the `expr_fragment_specifier_2024`
|
||||
//! rule.
|
||||
//! Migration code for the `expr_fragment_specifier_2024` rule.
|
||||
|
||||
use rustc_ast::token::{Token, TokenKind};
|
||||
use rustc_ast::tokenstream::{TokenStream, TokenTree};
|
||||
use rustc_session::lint::FutureIncompatibilityReason;
|
||||
|
|
|
@ -1,4 +1,5 @@
|
|||
#![cfg_attr(test, allow(dead_code))] // why is this necessary?
|
||||
|
||||
use super::abi::usercalls;
|
||||
use super::unsupported;
|
||||
use crate::ffi::CStr;
|
||||
|
|
|
@ -21,6 +21,7 @@ pub mod netc {
|
|||
//!
|
||||
//! Some Windows API types are not quite what's expected by our cross-platform
|
||||
//! 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 crate::sys::c::{self, ADDRESS_FAMILY, ADDRINFOA, SOCKADDR, SOCKET};
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue