rust-clippy/tests/ui/crashes/ice-5835.rs

#[rustfmt::skip]
pub struct Foo {
    /// 位	
    ///   ^ Do not remove this tab character.
    ///   It was required to trigger the ICE.
    pub bar: u8,
}

fn main() {}
Fix rustfmt error / Add comment for tab character 2021-04-10 12:43:52 +00:00			`#[rustfmt::skip]`
tabs_in_doc_comments: Fix ICE due to char indexing This is a quick-fix for an ICE in `tabs_in_doc_comments`. The problem was that we we're indexing into possibly multi-byte characters, such as '位'. More specifically `get_chunks_of_tabs` was returning indices into multi-byte characters. Those were passed on to a `Span` creation that then caused the ICE. This fix makes sure that we don't return indices that point inside a multi-byte character. However, we are still iterating over unicode codepoints, not grapheme clusters. So a seemingly single character like y̆ , which actually consists of two codepoints, will probably still cause incorrect spans in the output. 2021-04-06 04:59:10 +00:00			`pub struct Foo {`
			`/// 位`
Fix rustfmt error / Add comment for tab character 2021-04-10 12:43:52 +00:00			`/// ^ Do not remove this tab character.`
			`/// It was required to trigger the ICE.`
tabs_in_doc_comments: Fix ICE due to char indexing This is a quick-fix for an ICE in `tabs_in_doc_comments`. The problem was that we we're indexing into possibly multi-byte characters, such as '位'. More specifically `get_chunks_of_tabs` was returning indices into multi-byte characters. Those were passed on to a `Span` creation that then caused the ICE. This fix makes sure that we don't return indices that point inside a multi-byte character. However, we are still iterating over unicode codepoints, not grapheme clusters. So a seemingly single character like y̆ , which actually consists of two codepoints, will probably still cause incorrect spans in the output. 2021-04-06 04:59:10 +00:00			`pub bar: u8,`
			`}`

			`fn main() {}`