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

error: using tabs in doc comments is not recommended
  --> $DIR/ice-5835.rs:3:10
   |
LL |     /// 位    
   |           ^^^^ help: consider using four spaces per tab
   |
   = note: `-D clippy::tabs-in-doc-comments` implied by `-D warnings`

error: aborting due to previous error
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			`error: using tabs in doc comments is not recommended`
Fix rustfmt error / Add comment for tab character 2021-04-10 12:43:52 +00:00			`--> $DIR/ice-5835.rs:3:10`
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			`\|`
			`LL \| /// 位`
			`\| ^^^^ help: consider using four spaces per tab`
			`\|`
			= note: `-D clippy::tabs-in-doc-comments` implied by `-D warnings`

Fix rustfmt error / Add comment for tab character 2021-04-10 12:43:52 +00:00			`error: aborting due to previous error`
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