Remove double spaces after dots in comments
This commit is contained in:
parent
279f1c9d8c
commit
6a28fb42a8
157 changed files with 313 additions and 313 deletions
|
@ -1791,7 +1791,7 @@ impl EmitterWriter {
|
|||
|
||||
if let Some(span) = span.primary_span() {
|
||||
// Compare the primary span of the diagnostic with the span of the suggestion
|
||||
// being emitted. If they belong to the same file, we don't *need* to show the
|
||||
// being emitted. If they belong to the same file, we don't *need* to show the
|
||||
// file name, saving in verbosity, but if it *isn't* we do need it, otherwise we're
|
||||
// telling users to make a change but not clarifying *where*.
|
||||
let loc = sm.lookup_char_pos(parts[0].span.lo());
|
||||
|
@ -2529,11 +2529,11 @@ fn emit_to_destination(
|
|||
//
|
||||
// On Unix systems, we write into a buffered terminal rather than directly to a terminal. When
|
||||
// the .flush() is called we take the buffer created from the buffered writes and write it at
|
||||
// one shot. Because the Unix systems use ANSI for the colors, which is a text-based styling
|
||||
// one shot. Because the Unix systems use ANSI for the colors, which is a text-based styling
|
||||
// scheme, this buffered approach works and maintains the styling.
|
||||
//
|
||||
// On Windows, styling happens through calls to a terminal API. This prevents us from using the
|
||||
// same buffering approach. Instead, we use a global Windows mutex, which we acquire long
|
||||
// same buffering approach. Instead, we use a global Windows mutex, which we acquire long
|
||||
// enough to output the full error message, then we release.
|
||||
let _buffer_lock = lock::acquire_global_lock("rustc_errors");
|
||||
for (pos, line) in rendered_buffer.iter().enumerate() {
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue