# Brainstorming: how to help old code locked to old \`time\` build on new toolchains

**URL:** <https://internals.rust-lang.org/t/brainstorming-how-to-help-old-code-locked-to-old-time-build-on-new-toolchains/21438>\
**Category:** Uncategorized\
**Created:** [August 26, 2024, 3:59pm UTC](https://internals.rust-lang.org/t/brainstorming-how-to-help-old-code-locked-to-old-time-build-on-new-toolchains/21438 "2024-08-26T15:59:14Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![epage](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/epage/32/3171_2.png) [@epage](https://internals.rust-lang.org/u/epage)\
**Post date:** [August 26, 2024, 4:02pm UTC](https://internals.rust-lang.org/t/brainstorming-how-to-help-old-code-locked-to-old-time-build-on-new-toolchains/21438/2 "2024-08-26T16:02:33Z")

</div>

In [Workaround for type inference breakage in the time crate by kornelski · Pull Request #14452 · rust-lang/cargo · GitHub](https://github.com/rust-lang/cargo/pull/14452), the idea was proposed to have Cargo implicitly patch `registry+https://github.com/rust-lang/crates.io-index#time@0.3.18` through `registry+https://github.com/rust-lang/crates.io-index#time@0.3.34`.

There are implementation and correctness complexities to this. There are also likely corner cases in how it affects other aspects of the ecosystem (vendoring, nix, etc).

---

_[View the full topic](https://internals.rust-lang.org/t/brainstorming-how-to-help-old-code-locked-to-old-time-build-on-new-toolchains/21438)._