Skip to content

Conversation

@brentleyjones
Copy link
Collaborator

This was rarely caught in practice because it only affects implicit module compilation and only matters when a dependency has includes that depend on custom header search paths provided by one of their C dependencies.

PiperOrigin-RevId: 642596524
(cherry picked from commit 8600c56)

brentleyjones referenced this pull request Oct 22, 2024
… target that imports them.

This was rarely caught in practice because it only affects implicit module compilation and only matters when a dependency has includes that depend on custom header search paths provided by one of their C dependencies.

PiperOrigin-RevId: 642596524
@brentleyjones brentleyjones enabled auto-merge (rebase) October 22, 2024 20:36
@brentleyjones brentleyjones force-pushed the bj/don-t-drop-compilation-contexts-for-private_deps-when-compiling-the-target-that-imports-them branch from 4aed667 to 97e15ca Compare October 22, 2024 20:37
… target that imports them

This was rarely caught in practice because it only affects implicit module compilation and only matters when a dependency has includes that depend on custom header search paths provided by one of their C dependencies.

PiperOrigin-RevId: 642596524
(cherry picked from commit 8600c56)
Signed-off-by: Brentley Jones <[email protected]>
@brentleyjones brentleyjones force-pushed the bj/don-t-drop-compilation-contexts-for-private_deps-when-compiling-the-target-that-imports-them branch from 97e15ca to fcaa3ea Compare October 22, 2024 20:44
@brentleyjones brentleyjones merged commit 930bce3 into master Oct 22, 2024
@brentleyjones brentleyjones deleted the bj/don-t-drop-compilation-contexts-for-private_deps-when-compiling-the-target-that-imports-them branch October 22, 2024 20:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants