-
-
Notifications
You must be signed in to change notification settings - Fork 844
Comparing changes
Open a pull request
base repository: serde-rs/serde
base: v1.0.175
head repository: serde-rs/serde
compare: v1.0.176
- 16 commits
- 52 files changed
- 2 contributors
Commits on Aug 23, 2022
-
Configuration menu - View commit details
-
Copy full SHA for 9833474 - Browse repository at this point
Copy the full SHA 9833474View commit details
Commits on Jul 26, 2023
-
Delete unused serde_derive #[macro_use]
In old versions of rustc (1.15 through 1.29) it would cause a warning if this #[macro_use] was not present. warning: proc macro crates and `#[no_link]` crates have no effect without `#[macro_use]` --> serde/src/lib.rs:340:1 | 340 | extern crate serde_derive; | ^^^^^^^^^^^^^^^^^^^^^^^^^^ These days serde_derive requires a newer compiler than that, so the bogus warning would never occur.
Configuration menu - View commit details
-
Copy full SHA for 3260bc5 - Browse repository at this point
Copy the full SHA 3260bc5View commit details -
Move extern crate proc_macro into each possible lib.rs
This makes it slightly more convenient to use the following as a Reindeer fixup for those that prefer to build from source: extra_mapped_srcs = { "src/lib_from_source.rs" = "src/lib.rs" } [platform_fixups.'cfg(all(target_arch = "x86_64", target_os = "linux", target_env = "gnu"))'] extra_deps = [":proc-macro2", ":quote", ":syn"] as opposed to checking in a whole new file containing the `extern crate proc_macro` + `include!("lib_from_source.rs")`.
Configuration menu - View commit details
-
Copy full SHA for 6882285 - Browse repository at this point
Copy the full SHA 6882285View commit details -
Merge pull request #2532 from dtolnay/macrouse
Delete unused serde_derive #[macro_use]
Configuration menu - View commit details
-
Copy full SHA for 89f84c2 - Browse repository at this point
Copy the full SHA 89f84c2View commit details -
Configuration menu - View commit details
-
Copy full SHA for 30f79b3 - Browse repository at this point
Copy the full SHA 30f79b3View commit details -
Delete deprecated AsciiExt extension trait import
This has been superseded by inherent methods since Rust 1.26.
Configuration menu - View commit details
-
Copy full SHA for 26e2ef0 - Browse repository at this point
Copy the full SHA 26e2ef0View commit details -
Configuration menu - View commit details
-
Copy full SHA for 25a53f1 - Browse repository at this point
Copy the full SHA 25a53f1View commit details -
Merge pull request #2533 from dtolnay/test
Move serde_test out to serde-rs/test
Configuration menu - View commit details
-
Copy full SHA for 11677ad - Browse repository at this point
Copy the full SHA 11677adView commit details -
Configuration menu - View commit details
-
Copy full SHA for dd99136 - Browse repository at this point
Copy the full SHA dd99136View commit details -
Configuration menu - View commit details
-
Copy full SHA for 0fb672a - Browse repository at this point
Copy the full SHA 0fb672aView commit details -
Configuration menu - View commit details
-
Copy full SHA for b978854 - Browse repository at this point
Copy the full SHA b978854View commit details -
Configuration menu - View commit details
-
Copy full SHA for d2d7bad - Browse repository at this point
Copy the full SHA d2d7badView commit details -
Configuration menu - View commit details
-
Copy full SHA for 78a11a2 - Browse repository at this point
Copy the full SHA 78a11a2View commit details -
Configuration menu - View commit details
-
Copy full SHA for a6a8a33 - Browse repository at this point
Copy the full SHA a6a8a33View commit details -
Merge pull request #2266 from flisky/master
fix: don't check skipped variant with internal tag
Configuration menu - View commit details
-
Copy full SHA for b789286 - Browse repository at this point
Copy the full SHA b789286View commit details -
Configuration menu - View commit details
-
Copy full SHA for 85d5c1f - Browse repository at this point
Copy the full SHA 85d5c1fView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v1.0.175...v1.0.176