Set modified#84
Conversation
andrewhickman
left a comment
There was a problem hiding this comment.
This crate uses autocfg to allow wrapping new methods without bumping the MSRV. Please could you gate the new methods so they only appear in Rust 1.75+?
|
Ah. I see that now. I wasn't familiar with |
|
@andrewhickman, I believe I've handled gating these methods to Rust 1.75 with Let me know if there's anything else I should do here. |
|
That latest failure is on me (and only slightly embarrassing). Looks like I forgot to apply autocfg to the imports? |
|
Yeah, I believe that was the issue. I tested locally that this compiles now with rustup toolchain install 1.40
cargo +1.40 checkand saw only unused variant lints for I'm reasonably confident the CI should pass now. Please have another look when you're able and sorry for the trouble, @andrewhickman. Also, Happy Holidays! 🎄 |
|
I've released version 3.2.2 with this change. Thanks again and happy holidays! |
Forgive me if I've missed something rather major, but I think this will resolve #54 if I've done it correctly. I went ahead and did
File::set_timesas well because it seemed related, but didn't makeset_modifieda pass through toset_timeslikestd::fsbecause I think this way the error message is improved.I didn't add the corresponding methods for
tokiobecause they don't (yet) exist intokioitself. This was mentioned in tokio-rs/tokio#6368, but they're still waiting for a shift in MSRV before adding those methods. They're up to 1.71, but these methods weren't added until 1.75.If MSRV is an issue for this crate it'd be a bummer, but totally understandable.