• @[email protected]
    link
    fedilink
    22 days ago

    Just upgraded

    Weird wording!
    Maybe it’s just me, but this may give the impression that it’s something that is strictly needed, or will provide any immediate improvement, which is not the case, unless you’re still actively working on these projects and plan to use/depend on features/behaviors required by the new edition.

    • EpheraOP
      link
      fedilink
      English
      22 days ago

      Yeah, fair enough. I was mainly curious, how much would break, as in how quickly I might expect the Rust ecosystem to adopt these new features. Well, and unless there’s a reason against it, I’d prefer having everything on the same edition, i.e. the newest edition.

      • @[email protected]
        link
        fedilink
        02 days ago

        I might expect the Rust ecosystem to adopt these new features.

        This again points to you maybe not understanding how editions work, or maybe I’m just reading it wrong again. But you “upgrading” has no effect on your dependencies, and vise versa (except indirectly if MSRV is a factor as another user mentioned).

        • EpheraOP
          link
          fedilink
          English
          22 days ago

          I’m just talking about things like async closures looking like they might be really useful in a frontend framework we use. And I’m wondering when that framework’s documentation will recommend their usage. Or if there’s fancy things they can do with the AsyncFn traits.

          I will have to try out, if I can just pass an async closure without that framework changing anything. That’s the kind of thing where I am still unclear, how it will affect things. But the basic premise of editions isn’t lost on me, and this isn’t my first edition switchover either.