You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Outside macros and strings, this kind of thing will always fail to parse (seven equals signs in a row is always illegal), though the precise errors it will fail with will vary depends on the context.
It’d be nice if the compiler, on detecting a syntax error caused by merge conflict markers, gave a friendlier error message, something like this:
error: file contains merge conflict markers
--> <anon>:1:1
|
1 | <<<<<<< HEAD
| ^^^^^^^ merge conflict marker here
Take code like this:
Outside macros and strings, this kind of thing will always fail to parse (seven equals signs in a row is always illegal), though the precise errors it will fail with will vary depends on the context.
It’d be nice if the compiler, on detecting a syntax error caused by merge conflict markers, gave a friendlier error message, something like this:
(Inspiration: Perl 5.26.0 produces a syntax error like “Version control conflict marker at line 123” thanks to https://rt.perl.org/Public/Bug/Display.html?id=127993.)
The text was updated successfully, but these errors were encountered: