Pras Velagapudi

I'm not sure I quite follow the implications here. Maybe you could point to some examples of when this is bad? > For instance functions like getMetaSkeleton() are trivial and...

Thanks for the explanation, @jslee02. > `b.foo(); // Error w/o adding "using A::foo" to B` Is this a compile-time error or a runtime error? > @aditya-vk basically suggest making both...

I am thinking the same thing. While it is annoying that the compiler does not give a better error, it does seem that this is a _compile-time_ issue, meaning that...

@yuwenma : I am not sure about the PR author, but [in the original issue](https://github.com/kubernetes-sigs/kustomize/issues/4593), you can see a number of folks who have use cases that are affected. Generally,...

Implemented in https://github.com/jbeder/yaml-cpp/pull/1069

Looking at the source, there are actually two things that get put in `$EXT_BUILD_DEPS/include`: `headers` and `include_dirs`: https://github.com/bazelbuild/rules_foreign_cc/blob/83a0c2a9b1e83b98c3d9546a64518e8bd480ad50/tools/build_defs/framework.bzl#L580 While the `headers` are passed as a list of files that gets...

As far as I can tell, the desired behavior would always be to replicate the directory structure of the source with `include_prefix` and `strip_include_prefix`. I can see no use case...

bump, still affected by this issue

My workaround is a bash script that searches by pattern for this file. Thankfully, `py_wheel` are not typically consumed by other rules. I reported this because it's not documented behavior,...

I think this might mean we need to go with (2), as that's the only way I can see to get compliance here. In the current form, the internal `dist-info`...