GitHub user Xuanwo added a comment to the discussion: Which version of MSRV should be next?
> So before the release of version 1.0, does the opendal community currently > have a specific MSRV upgrade strategy? We have an MSRV but haven't established a strategy yet. We are using `1.75` because we really need `return_position_impl_trait_in_trait` and `async_fn_in_trait`. That's why I'm talking about "strong enough". > Maybe we can discuss it here and make a specific rule? That's will be nice. > For example, the MSRV of the latest version of opendal (only used for 0.x > versions) will be several versions ahead of the latest version of rust. Feel free to propose different strategies. Clearly, there's a trade-off: a newer MSRV lets us use the latest features and maintain code more easily, while an older MSRV enables more users to access OpenDAL (this is SUPER important for us). We need to balance these considerations. Perhaps we could gather more data, such as which versions are most commonly used by Rust users (aiming to support 90% or 95% of them) or which versions are most used by OpenDAL's users (more useful but potentially harder to collect). GitHub link: https://github.com/apache/opendal/discussions/5253#discussioncomment-11101257 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
