feat(rust): count ? try operator in complexity

[daulet]

  fn parse<T: ?Sized>(s: &str) -> Result<i32, Error> {
      let n = s.trim().parse()?;
      if n > 0 {
          Ok(n + lookup(n)?)
      } else {
          Err(Error::Negative)
      }
  }

  ┌────────┬─────────────────────────────────────┐
  │        │             Complexity              │
  ├────────┼─────────────────────────────────────┤
  │ before │ 2 — if, else                        │
  ├────────┼─────────────────────────────────────┤
  │ after  │ 4 — if, else, ? (parse), ? (lookup) │
  └────────┴─────────────────────────────────────┘

[Copilot]

Pull request overview

Adds support for counting Rust’s postfix ? try operator toward cyclomatic complexity by introducing a new “postfix complexity token” mechanism in the processor, and wiring it through the language definitions pipeline (JSON → generated constants → runtime token tries).

Changes:

• Extend language definitions to support complexitychecks_postfix (JSON + generator template + Go structs/constants).
• Add a new token type (TComplexityPostfix) and matching logic in the hot-path tokenizer/state machine.
• Add Rust-specific tests to verify ? is counted while ?Sized is not.

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
scripts/languages.tmpl	Generate ComplexityChecksPostfix into languageDatabase when present.
languages.json	Add Rust complexitychecks_postfix: ["?"].
processor/constants.go	Generated update: Rust now includes ComplexityChecksPostfix: []string{"?"}.
processor/structs.go	Add TComplexityPostfix and extend Language with ComplexityChecksPostfix.
processor/processor.go	Insert postfix complexity tokens into the token trie and process mask.
processor/workers.go	Implement counting logic for TComplexityPostfix and add isIdentifierStart helper.
processor/workers_test.go	Add tests for Rust ? counting and ?Sized non-counting.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[boyter]

Thanks for this. This is one of those ones I have wanted for a while but never tackled... probably because I dont do much rust.