Replies: 5 comments 12 replies
-
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
Thanks for putting this together! Triage results, in the same order as you mentioned them:
I'm certainly open to experimenting with the way the tool reports results, including grouping by file, adding color, etc. I wasn't sure how to best frame that as an issue, but if you think one would be useful then we can work together on adding it. The performance is slowing down as we add more lints, and I'm afraid will get slightly worse when we account for more kinds of re-exports. We can look into using I'm still looking at the |
Beta Was this translation helpful? Give feedback.
-
Something else is that the change in a where clause was missed
This was intentional but I lost track when doing the changelog. |
Beta Was this translation helpful? Give feedback.
-
I also started looking into the performance issue you highlighted, and something seriously doesn't add up. I'll ignore rustdoc build timing since that's sensitive to a lot of caching etc. that is not trivial to control for. I'll only compare the checks-only time reported in your printouts and on my machine, a ~3yr old laptop with an Intel Core i7-10875H CPU @ 2.30GHz 8-core 16-thread CPU. For That's a shockingly large difference, especially since I'm on a thermally-limited laptop that can't boost its CPU frequency that high to take advantage of the single-threaded workload. No merged PRs between the commit where you tested and present could have come even close to having that kind of impact. I also seriously doubt my outdated laptop is that much faster than your computer. Can you verify that you ran the tests with |
Beta Was this translation helpful? Give feedback.
-
I'm preparing for a major change to both of these crates and figured I'd run this. I have not bumped versions yet though both will have a breaking change, so I'm seeing everything.
This is running
main
(cf1e270) againstmain
of toml / toml_edit (d86370fc5e8777e532de457cb6569feeae6429f0).General thoughts
toml_edit
, my shell prompt said it took 18s, with the tool reporting the checkss completed in 11s and the final as 16stoml
was a bit better with 6s, 4s, 4stoml_edit:
toml_edit::Value
no longer impls a lot of types thatcargo doc
says it still implsError
struct (with private fields) to an enum but it considered this a breaking change when I don't think it istoml:
Error
enum to a struct. Saying it was removed is wrong, it only changed in how it can be constructed. All the inherent methods and trait impls should still be compared between them.toml_datetime
crate and re-export them but they were reported as removedI can't think of an API changes that weren't reported. I would have liked to see API items added as well. A very strict reading of semver says that API adds are for minor versions. I would also like to see it to help write the changelog. More importantly, when I don't trust the tool, seeing what the tool considers an add would help build trust in what the tool is doing (e.g. I would see an enum-add paired with my struct-remove)
Beta Was this translation helpful? Give feedback.
All reactions