Python fp and docs updtes (#58)

* refactor: Update comments for clarity and add expectations.json files for performance metrics

* feat: Implement FP guard for JS/TS local-collection receivers to suppress missing ownership checks

* feat: Enhance Rust parameter handling to classify local collections and prevent false ownership checks

* refactor: Simplify code formatting for better readability in multiple files

* refactor: Improve UTF-8 sequence length handling and enhance clarity in loop iteration

* feat: Update Java and Python patterns to include new security rules

* refactor: Improve comment clarity and consistency across multiple Rust files

* refactor: Simplify code formatting for improved readability in integration tests and module files

* refactor: Improve comment formatting and enhance clarity in assertions across multiple files
This commit is contained in:
Eli Peter 2026-04-29 19:53:34 -04:00 committed by GitHub
parent 4db0805de6
commit a438886217
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
291 changed files with 9485 additions and 3851 deletions

View file

@ -45,7 +45,7 @@ fn build_bulk_source(bytes_target: usize) -> String {
#[test]
fn parse_timeout_config_short_circuits_parse() {
// ~1 MiB of valid JS plenty of real parser work to observe the
// ~1 MiB of valid JS, plenty of real parser work to observe the
// timeout. Still well under MAX_PARSE_BYTES.
let source = build_bulk_source(1_000_000);
@ -68,7 +68,7 @@ fn parse_timeout_config_short_circuits_parse() {
// A timed-out parse surfaces a synthetic informational diag
// carrying an `EngineNote::ParseTimeout` so downstream tooling can
// tell "we found nothing" from "we stopped looking". Any other
// finding would imply the parser actually produced a tree i.e.
// finding would imply the parser actually produced a tree, i.e.
// the timeout did not short-circuit.
assert!(
diags.iter().all(|d| d.id == "engine.parse_timeout"),