Today, I happened to use a raw string that wasn't highlighted correctly in Rust. The
problem was that using a . in a regex in SEQ_REGEXP does not match newlines, so I
switched to using SPAN_REGEXP. I also added HASH_CHAR to a couple tags.
I updated the file I've been using for testing to include the string that wasn't highlighted
correctly:
https://gist.github.com/jminer/401fafd13107d512a40f
Submitted | jminer7 - 2015-10-24 20:27:38.075000 | Assigned | |
---|---|---|---|
Priority | 5 | Labels | |
Status | open | Group | None |
Resolution | None |
2015-11-08 06:44:34.723000 jminer7 |
I didn't notice that adding HASH_CHAR to the rule that highlights lifetimes broke the character literal rule. I've added HASH_CHARS to that rule and it works again. The first patch can be ignored, and this one used instead. rust_raw_string_fix2.patch (1.3Kio) |
---|