Sound specialization

1

Hi,
https://github.com/rust-lang/trait-system-refactor-initiative/issues/39

What does it mean exactly: statu quo with the current compiler interpretation or specialization is indeed sound now?

Thanks

2

Given that the issue was closed 2 years ago, with no comments before or after that, I don't think it represents any recent advances on the subject. To my knowledge, even #![feature(min_spec)], despite the whole idea being roughly "it's only the sound bits", is still unsound.

3

AFAICT the issues in that repo are about making the unstable feature work with the new solver, and not about completing the feature itself per se (though I doubt that or any other major type system feature will land before the new solver).

This is the specialization tracking issue. My take from the labels and recentish comments is that min_specialization won't be stabilized without some sort of formalization or redo (new RFC or such).[1] That said, I'm not on any teams. It has some outstanding bugs with at least one of them being unsound.

  1. specialization is known to be incomplete and unsound, and won't be stabilized. ↩ī¸Ž