> why not just call it a version conflict and fail until it's resolved Because its unnecessary and it doesn't scale. In Rust, versions become part of the symbo

> why not just call it a version conflict and fail until it's resolved Because its unnecessary and it doesn't scale. In Rust, versions become part of the symbol name, and the whole thing just becomes a non-issue. Go did the right thing here.