Skip to content

Eliminate try/catch in parse if present to help V8 deoptimize less #70

@alanzabihi

Description

@alanzabihi

V8 sometimes deopts functions containing try/catch blocks. Check src/index.ts for any try/catch in parse's code path. If present (likely for format function or number coercion), move outside the hot path. Fingerprint exact. Target: potential 0.5-1ms if V8 was deopting; probably neutral since parse() is simple.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions