https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.86.0 2025-01-21T13:48:44+00:00 2025-01-21T13:48:44+00:00 klensy klensy@users.noreply.github.com 2025-01-14T13:57:04+00:00 urn:sha1:84ce2e129a5b6a5af2f2ea27af5ad907a1aac419 2024-12-17T04:34:46+00:00 Harrison Kaiser uwaces@gmail.com 2024-12-16T01:06:02+00:00 urn:sha1:1e33dd17115ca948c6e5ebf319695ed64490b2bf There is a logical issue around what counts as leading white-space. There is code which does a subtraction assuming that no errors will be reported inside the leading whitespace. However we compute the length of that whitespace with std::char::is_whitespace and not rustc_lexer::is_whitespace. The former will include a no-break space while later will excluded it. We can only safely make the assumption that no errors will be reported in whitespace if it is all "Rust Standard" whitespace. Indeed an error does occur in unicode whitespace if it contains a no-break space. 2024-11-12T13:38:58+00:00 Noratrieb 48135649+Noratrieb@users.noreply.github.com 2024-10-28T17:51:12+00:00 urn:sha1:505b8e133282a5ced49d8b9c6c5678b8030123a4 Since it's inception a long time ago, the parallel compiler and its cfgs have been a maintenance burden. This was a necessary evil the allow iteration while not degrading performance because of synchronization overhead. But this time is over. Thanks to the amazing work by the parallel working group (and the dyn sync crimes), the parallel compiler has now been fast enough to be shipped by default in nightly for quite a while now. Stable and beta have still been on the serial compiler, because they can't use `-Zthreads` anyways. But this is quite suboptimal: - the maintenance burden still sucks - we're not testing the serial compiler in nightly Because of these reasons, it's time to end it. The serial compiler has served us well in the years since it was split from the parallel one, but it's over now. Let the knight slay one head of the two-headed dragon! 2024-10-28T04:10:58+00:00 Jubilee Young workingjubilee@gmail.com 2024-10-28T03:38:33+00:00 urn:sha1:4839d6e6e51f29c6bd9b581df520a8f1a6d278b9 Depend on rustc_abi in compiler crates that use it indirectly but have not yet taken on that dependency, and are not entangled in my other PRs. This leaves an "excise rustc_target" step after the dust settles. 2024-09-27T06:23:05+00:00 klensy klensy@users.noreply.github.com 2024-09-24T13:14:49+00:00 urn:sha1:26c09b6553733a0849c30845909a52a6d210b8da cargo_metadata, thorin-dwp, windows 2024-08-19T20:22:07+00:00 Xiretza xiretza@xiretza.xyz 2024-08-19T20:20:48+00:00 urn:sha1:c864238baf2d44e1634c754451d69e66ef56201b 2024-07-18T20:08:38+00:00 Esteban Küber esteban@kuber.com.ar 2024-07-09T17:00:19+00:00 urn:sha1:2d7795dfb942d49d447837ef43db89216de15696 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␀![{i | -- unclosed delimiter | | | unclosed delimiter LL | ␀␀ fn rݻoa>rݻm | ^ ``` 2024-02-18T13:02:16+00:00 klensy klensy@users.noreply.github.com 2024-02-18T13:02:16+00:00 urn:sha1:35fe26757adce8cd8d1b9e7f4107a0ac9a7ab27b 2024-01-28T20:41:41+00:00 Nicholas Nethercote n.nethercote@gmail.com 2024-01-13T23:57:07+00:00 urn:sha1:5d9dfbd08f38c2a9bc71d39de8f5c7776afe0f9e Error codes are integers, but `String` is used everywhere to represent them. Gross! This commit introduces `ErrCode`, an integral newtype for error codes, replacing `String`. It also introduces a constant for every error code, e.g. `E0123`, and removes the `error_code!` macro. The constants are imported wherever used with `use rustc_errors::codes::*`. With the old code, we have three different ways to specify an error code at a use point: ``` error_code!(E0123) // macro call struct_span_code_err!(dcx, span, E0123, "msg"); // bare ident arg to macro call \#[diag(name, code = "E0123")] // string struct Diag; ``` With the new code, they all use the `E0123` constant. ``` E0123 // constant struct_span_code_err!(dcx, span, E0123, "msg"); // constant \#[diag(name, code = E0123)] // constant struct Diag; ``` The commit also changes the structure of the error code definitions: - `rustc_error_codes` now just defines a higher-order macro listing the used error codes and nothing else. - Because that's now the only thing in the `rustc_error_codes` crate, I moved it into the `lib.rs` file and removed the `error_codes.rs` file. - `rustc_errors` uses that macro to define everything, e.g. the error code constants and the `DIAGNOSTIC_TABLES`. This is in its new `codes.rs` file. 2024-01-07T13:53:32+00:00 klensy klensy@users.noreply.github.com 2023-12-30T15:11:41+00:00 urn:sha1:5b153b52a25dfe4c9592dd6c9f47582018b4fa61