aboutsummaryrefslogtreecommitdiff
path: root/crates/syntax/test_data/reparse/fuzz-failures/0000.rs
diff options
context:
space:
mode:
authorbors[bot] <26634292+bors[bot]@users.noreply.github.com>2021-02-17 11:58:35 +0000
committerGitHub <[email protected]>2021-02-17 11:58:35 +0000
commit5cd7a0f2c5a7948dcd6b1838e1497c560d5c65a1 (patch)
treed019f37897f2902244ff726dacbf19346e23d4d5 /crates/syntax/test_data/reparse/fuzz-failures/0000.rs
parent2920e7b28b58400a9026e92f28fc0304d71c7376 (diff)
parent528a0bcf9b0e4ad1e89d21c9c8df3c55aa3ade00 (diff)
Merge #7704
7704: Avoid transmitting unchanged diagnostics r=matklad a=michalmuskala Reading through the code for diagnostics and observing debug logs, I noticed that diagnostics are transmitted after every change for every opened file, even if they haven't changed (especially visible for files with no diagnostics). This change avoids marking files as "changed" if diagnostics are the same to what was already sent before. This will only work if diagnostics are always produced in the same order, but from my limited testing it seems this is the case. Co-authored-by: Michał Muskała <[email protected]>
Diffstat (limited to 'crates/syntax/test_data/reparse/fuzz-failures/0000.rs')
0 files changed, 0 insertions, 0 deletions