Replies: 7 comments 25 replies
-
|
1.64 gets us |
Beta Was this translation helpful? Give feedback.
-
|
1.56 gets us edition 2021 which is the main cause of all the MSRV breakage we get, preventing that would be super awesome. |
Beta Was this translation helpful? Give feedback.
-
|
I was patching Rust 1.63 allows use to depend on |
Beta Was this translation helpful? Give feedback.
-
|
As we start to release v1.0 of our crates starting at the bottom ( |
Beta Was this translation helpful? Give feedback.
-
|
FTR LDK is bumping their MSRV to 1.63. I think we should target no less than that for stabilization which will still take a long time. |
Beta Was this translation helpful? Give feedback.
-
|
I've been thinking about |
Beta Was this translation helpful? Give feedback.
-
|
For completeness sake: At the Rust Bitcoin Summit in Nashville in 2025 we discussed this and came to consensus that |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
EDIT(tcharding) TL;DR Rust 1.74 (see bottom of thread for why).
Newer Rust versions allow us to make the API better in ways that would require breaking the API if we wanted to improve it later. However we don't want to wait infinitely long since any release may add such possibility. So we should set some MSRV we want to stabilize at.
Interesting versions:
1.46 - not sure if it actually helps the API but allowswe're already at 1.48AsRef<T>for all[T; N][u8; Self::LEN]instead ofSelf::InnerinHash.constfn - could improveconstAPI, not sure how relevantno-stdfeatureBeta Was this translation helpful? Give feedback.
All reactions