This past reliance doesn't work well with Swift, and the sources were trying to over hand optimize to minimize rebuilds, and that likely isn't worth the trouble, so explicit imports. The remaining places that still use them are where they are needed within the header to deal with relationships between the local definitions or where there is a cycle between the headers and it allows either one to be imported first and still get a complete definition in the using context. PiperOrigin-RevId: 671379912pull/18098/head
parent
3c3d4900bc
commit
231b968b9c
20 changed files with 44 additions and 38 deletions
Loading…
Reference in new issue