{"version":"2.1.229","anchor":"faster-new-diagnostic-detection-and-none-at-all-without-a-ba","canonical_anchor":"faster-new-diagnostic-detection-and-none-at-all-without-a-ba","heading":"Faster new-diagnostic detection, and none at all without a baseline","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/faster-new-diagnostic-detection-and-none-at-all-without-a-ba","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Faster new-diagnostic detection, and none at all without a baseline\n\nDetecting new editor diagnostics after an edit is faster and skipped entirely without a baseline.\n\n**What**\n\nComparing editor diagnostics before and after an edit now hashes each one (message, severity, source, code, range) into a set instead of comparing every diagnostic against every other, and when there is no earlier snapshot to compare against it returns immediately without even asking the IDE for diagnostics. Less CPU and one fewer round-trip on files that were never snapshotted.\n\n**Evidence**\n\n`getDiagnostics`\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}