Trevor Gross
999967a57d
Rename cfg_match! to cfg_select!
...
At [1] it was pointed out that `cfg_match!` syntax does not actually
align well with match syntax, which is a possible source of confusion.
The comment points out that usage is instead more similar to ecosystem
`select!` macros. Rename `cfg_match!` to `cfg_select!` to match this.
Tracking issue: https://github.com/rust-lang/rust/issues/115585
[1]: https://github.com/rust-lang/rust/issues/115585#issuecomment-2346307605
2025-05-20 21:16:23 +00:00
Eric Huss
a78d1b092c
Update stdarch
2025-03-06 11:11:55 -08:00
real-eren
62f5a5501f
Use as_chunks in analyze_source_file_sse2
2025-02-23 13:59:27 -05:00
Josh Stone
3c45324e67
update cfg(bootstrap)
2025-02-18 09:32:44 -08:00
real-eren
d6ca7ad0d7
Remove dead control char logic
...
Only newlines and multibyte characters are actually relevant
2025-02-02 21:51:56 -05:00
real-eren
3c7c38ad93
Simplify SSE2 implementation
2025-02-02 21:51:56 -05:00
Caio
c89f0dc01d
Adjust syntax
2024-12-22 17:12:42 -03:00
Nicholas Nethercote
b0f22ff98f
Add warn(unreachable_pub) to rustc_span.
2024-09-03 08:49:54 +10:00
Esteban Küber
2d7795dfb9
Be more accurate about calculating display_col from a BytePos
...
No longer track "zero-width" chars in `SourceMap`, read directly from the line when calculating the `display_col` of a `BytePos`. Move `char_width` to `rustc_span` and use it from the emitter.
This change allows the following to properly align in terminals (depending on the font, the replaced control codepoints are rendered as 1 or 2 width, on my terminal they are rendered as 1, on VSCode text they are rendered as 2):
```
error: this file contains an unclosed delimiter
--> $DIR/issue-68629.rs:5:17
|
LL | ␜␟ts␀