Prerequisites

• Put an X between the brackets on this line if you have done all of the following:
  • Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
  • Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
  • Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
  • Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
  • Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description

Including an assignment attribute inside a proc. macro (i.e. #[x(y = z)]) followed by a string literal breaks the current rust syntax parser.

Steps to Reproduce

1. Open a new file, with the syntax highlighter set to Rust.
2. Enter the following code:

   #[x(y = z)]
   struct W();
   
   let x = "hello";
   

3. After the introduction of the string literal, the highlighting breaks.

Expected behavior:

The syntax highlighting should continue to work.

Actual behavior:

It reproduces 100% of the time, even in more complex situations.

Versions

Atom    : 1.47.0
Electron: 5.0.13
Chrome  : 73.0.3683.121
Node    : 12.0.0
MacOS   : 10.15.5 

Additional Information

I suspect that the parser is looking for a string literal in the attribute in a greedy manner and gets confused when it encounters one later.