rust/tests/ui/parser/macro, branch cargo_update https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=cargo_update 2025-09-26T13:33:48+00:00 Ignore more failing ui tests for GCC backend 2025-09-26T13:33:48+00:00 Guillaume Gomez guillaume1.gomez@gmail.com 2025-09-26T11:59:06+00:00 urn:sha1:a535c7be5444fb6584eecc99f53e6cdb710ff70f mbe: Parse macro `derive` rules 2025-08-14T20:53:57+00:00 Josh Triplett josh@joshtriplett.org 2025-08-09T22:16:19+00:00 urn:sha1:8fb98ef36846f74c8a642e856808ad5600ae4110 This handles various kinds of errors, but does not allow applying the derive yet. This adds the feature gate `macro_derive`. mbe: Add parser test for macro attribute recovery 2025-08-08T18:01:12+00:00 Josh Triplett josh@joshtriplett.org 2025-08-08T17:17:43+00:00 urn:sha1:9a9ccc0edbf50428d0f12441cf50f32d5ea0f558 mbe: Parse macro attribute rules 2025-08-08T18:00:54+00:00 Josh Triplett josh@joshtriplett.org 2025-07-06T22:15:01+00:00 urn:sha1:bad0d45b2dc2b2be36e9e82604a6c3dd95dba08a This handles various kinds of errors, but does not allow applying the attributes yet. This adds the feature gate `macro_attr`. Rename tests named with `mbe` to use `macro` instead 2025-07-06T04:09:10+00:00 Josh Triplett josh@joshtriplett.org 2025-07-05T23:57:24+00:00 urn:sha1:131cffb6baca60f119c33f2599a0e6051b05c365 Most macro tests use `macro` in the name, making it easy to find and run tests relevant to macros. However, a few use `mbe` instead. Rename those to say `macro`. Move macro tests in `parser` into `macro` directory 2025-07-05T23:52:59+00:00 Josh Triplett josh@joshtriplett.org 2025-07-05T23:52:59+00:00 urn:sha1:6d64306df1d834966a23a27c085c043214668181 The `macro` directory contains most of the macro tests, but not all of them; move the remainder into `macro`. mbe: Gracefully handle macro rules that end after `=>` 2025-07-04T03:56:05+00:00 Josh Triplett josh@joshtriplett.org 2025-07-04T03:53:10+00:00 urn:sha1:0403990000438742065e54c4cae9bb1afb0e6038 Add a test for various cases of invalid macro definitions. Closes: https://github.com/rust-lang/rust/issues/143351 mbe: Clean up code with non-optional `NonterminalKind` 2025-06-24T08:37:36+00:00 Trevor Gross tmgross@umich.edu 2025-06-18T02:15:38+00:00 urn:sha1:b9e9be38c01104dd7e1a23995ef89995357bd35b Since [1], the fragment specifier is unconditionally required in all editions. This means `NonTerminalKind` no longer needs to be optional, as we can reject this code during the expansion of `macro_rules!` rather than handling it throughout the code. Do this cleanup here. [1]: https://github.com/rust-lang/rust/pull/128425 Make `missing_fragment_specifier` an unconditional error 2025-06-12T07:57:12+00:00 Trevor Gross tmgross@umich.edu 2024-07-31T03:04:23+00:00 urn:sha1:841f7ce69ac503fb9566deeefbbd273c1587f4e6 This was attempted in [1] then reverted in [2] because of fallout. Recently, this was made an edition-dependent error in [3]. Make missing fragment specifiers an unconditional error again. [1]: https://github.com/rust-lang/rust/pull/75516 [2]: https://github.com/rust-lang/rust/pull/80210 [3]: https://github.com/rust-lang/rust/pull/128006 Report text_direction_codepoint_in_literal when parsing 2025-05-27T15:57:41+00:00 Matthew Jasper mjjasper1@gmail.com 2025-05-14T10:43:39+00:00 urn:sha1:65bdb31a97af553c4fd932a171b74eaad76c1c53 - The lint is now reported in code that gets removed/modified/duplicated by macro expansion. - Spans are more accurate - Fixes #140281