> I could picture a future where the Compiler Team realizes we have an important question about the behavior of the software, that could be answered by analyzing these metrics, and have a VSCode or cargo plugin that analyzes these metrics locally, and if relevant information is found in these logs an appropriate summary is presented to the user for them to file a ticket.
The concept described is that the compiler would generate these metrics locally and store them for a limited period of time, but there would be no built in method for those metrics to leave the system they were generated on.
The user would then have that data available for their own use and could choose to manually share it or independently install a service to automatically share it per their own needs and desires.
So basically collecting the metrics but with no phone-home method built in. The user action to provide consent for access to the data is actually sharing the data.
> Without user action the data would never go anywhere.
What is the user action?
I wish this was worded in a more specific way. Like: without user’s opt in the data would never go anywhere. Or: without user’s explicit consent (type “yes” to share data) the data would not go anywhere. Is either correct here?