3 ms·
The problem with the current approach is that it does not specify whether `libfoo-1.2.3[unstable-bar]` is compatible with `libfoo-1.3.4[unstable-bar]`, nor whet
by o11c 3y ago
The problem with the current approach is that it does not specify whether `libfoo-1.2.3[unstable-bar]` is compatible with `libfoo-1.3.4[unstable-bar]`, nor whether the latter is compatible with `libfoo-1.4.5[default]`.
(also I'm not sure under what circumstances recompilation is required)
- conradludgate 3y agoThe rust std lib doesn't make any commitments to unstable (nightly) APIs, so this is the norm.
- o11c 3y agoIt doesn't formally make commitments. But in practice for most particular APIs there is stability, and it is the job of tooling to support that.