Gracefully handle ternary operator

[Centri3]

Fixes #112578

May not be the best way to do this as it doesn't check for a single :, so it could perhaps appear even when the actual issue is just a missing semicolon. May not be the biggest deal, though?

Nevermind, got it working properly now ^^

[rustbot]

r? @davidtwco

(rustbot has picked a reviewer for you, use r? to override)

[compiler-errors]

gotta do a perf run cause parser is larger

@bors try @rust-timer queue

[bors]

⌛ Trying commit faa7395 with merge bd6b819d60ffdfdba3010b39e4097b59d1aafb85...

[Centri3]

I actually just removed the maybe_ternary_lo field, so it should be the same size again. But yeah a perf run is wise

[compiler-errors]

@bors r+

[bors]

📌 Commit 79b6ed0 has been approved by compiler-errors

It is now in the queue for this repository.

[bors]

⌛ Testing commit 79b6ed0 with merge a04e649...

[bors]

☀️ Test successful - checks-actions
Approved by: compiler-errors
Pushing a04e649 to master...

[rust-timer]

Finished benchmarking commit (a04e649): comparison URL.

Overall result: no relevant changes - no action needed

@rustbot label: -perf-regression

Instruction count

This benchmark run did not return any relevant results for this metric.

Max RSS (memory usage)

Results

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	1.8%	[1.8%, 1.8%]	1
Improvements ✅ (primary)	-1.6%	[-3.5%, -0.7%]	19
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	-1.6%	[-3.5%, -0.7%]	19

Cycles

This benchmark run did not return any relevant results for this metric.

Binary size

This benchmark run did not return any relevant results for this metric.

Bootstrap: 651.386s -> 652.746s (0.21%)