Of course, but I'd like to start socializing the ideas so when the transition is complete we can hit the ground running. I don't want to hold up the ecosystem longer than we have to.
Which to your question @taylorswift, we need to see what that Pitch means in the Swift Build context. It may mean implementing it twice. But I'd like to see more analysis on the Pitch about the pros and cons. We have a lot of features that have been bolted on to SwiftPM that may have been better done if we took a step back and made a bigger change that gave us a bigger benefit. Once a feature is in, we can't really take it back as people start to use it.