-
Notifications
You must be signed in to change notification settings - Fork 17.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
testing: move Internal types to internal package #35567
Comments
This seems like a likely accept given the reactions over the past two weeks. Leaving open for a week for final comments. |
No change in consensus, so accepting. |
Hey @bradfitz! Sorry for pinging, but I'd like to take a stab on this issue if that's okay with you! From what I gather, we'd like move InternalBenchmark, InternalExample, and InternalTest into a new package most likely in Then, to avoid confusion during a couple of releases, we'd also like to alias them to their older names like I hope I'm not completely off the mark; please let me know if I've missed anything and I'll try to get a CL opened soon! |
I tried my hand on this; moving It cascades to more changes than I anticipated, but I'll still open that CL in the next days and hopefully get some feedback. |
Change https://golang.org/cl/247057 mentions this issue: |
@arnottcr took a stab at this in https://golang.org/cl/247057, and the resulting change is pretty big and has ramifications like changing the names of user visible types. Unless we can find a simpler approach, I don't think we should actually do this. |
While I find it problematic that one of the blocking arguments is that, type alias documentation is a bad ux and #44905 was closed without resolution; I agree this change is probably too large to justify otherwise, should we close it out? |
I agree - we did not consider the references InternalTest -> T and InternalBenchmark -> B. |
InternalBenchmark, InternalExample, and InternalTest predate the "internal" package mechanism.
Per a discussion here, we could probably move those three into a new internal package, and add a type alias for a few cycles before removing the testing alias.
The text was updated successfully, but these errors were encountered: