Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

⚡️ Perf: Run performance comparison for ts.JSDocParsingMode.ParseForTypeInfo #7906

Open
Labels
performanceIssues regarding performanceteam assignedA member of the typescript-eslint team should work on this.
@JoshuaKGoldberg

Description

@JoshuaKGoldberg

Suggestion

Splitting out ofhttps://devblogs.microsoft.com/typescript/announcing-typescript-5-3-beta/#optimizations-by-skipping-jsdoc-parsing ->#7821 (comment): we'd like to use the newJSDocParsingMode flag. But how beneficial is it, exactly? Let's run some kind of performance comparison to see.

From@bradzacher:

My original perf profiling way back when showed a decent chunk of time spent but things may have changed since then.
Note: the more important time would be the non-type-aware lint time as type info would dwarf any savings we get.

#7870 is an example of me setting up a Hyperfine comparison.

Metadata

Metadata

Assignees

No one assigned

    Labels

    performanceIssues regarding performanceteam assignedA member of the typescript-eslint team should work on this.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions


      [8]ページ先頭

      ©2009-2025 Movatter.jp