Rust: avoid panic from line_index crate

[redsun82]

We found out we can stumble upon a line_index.line_col panic, specifically when reporting a macro parse error.

This replaces line_col with safer try_line_col, and deals more gracefully with the error.

[Copilot]

PR Overview

This pull request addresses a potential panic scenario when using the line_index crate by replacing calls to line_index.line_col with the safer try_line_col. Key changes include adding a constant for a fallback unknown location, updating the location() function to return an Option with proper error propagation, and adjusting its callers to handle the new behavior gracefully.

Changes

File	Description
rust/extractor/src/translate/base.rs	Replaces direct line_col calls with try_line_col; updates error handling and control flow to avoid panics in diagnostic reporting

Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.

Comments suppressed due to low confidence (2)

rust/extractor/src/translate/base.rs:84

• [nitpick] Consider adding a comment explaining the rationale behind using (0, 0) for UNKNOWN_LOCATION to aid future maintenance and clarify its intended fallback behavior.

const UNKNOWN_LOCATION: (LineCol, LineCol) =

rust/extractor/src/translate/base.rs:215

• Using unwrap_or with UNKNOWN_LOCATION may hide issues with location resolution; consider logging a warning or error when try_line_col fails to improve diagnostic traceability.

location.unwrap_or(UNKNOWN_LOCATION)

Tip: If you use Visual Studio Code, you can request a review from Copilot before you push from the "Source Control" tab. Learn more

[paldepind]

Looks great!