Could PyTorch use language editions to remove old footguns?
Breaking default changes are hard in mature frameworks, and edition-style opt-ins could let PyTorch batch safety improvements without fragmenting the ecosystem
One of the reasons some footguns in PyTorch persist is because it would be BC-breaking to change the defaults. I'm kind of wondering if something like language editions (similar to C++20) could help us batch defaults updates and make them m