Pedro

> > what about linking? Is the rule that the C++ compiler should be used if there is at least one object file that was built from C++? > >...

The fix is to replace this line: https://cs.opensource.google/bazel/bazel/+/master:src/main/starlark/builtins_bzl/common/cc/cc_binary_attrs.bzl;drc=db36147bc66109cc2f34bcdb5bb8829182ef0346;l=65 with `providers = [CcInfo]` A PR is welcome.

It might be that this gathers steam at the beginning of next year but I can't promise anything. In any case, it would be clang modules, not C++20 modules. Whoever...

Yes, you can create a separate issue for tracking C++20 module support. Be aware though that as it looks right now it will be a long time before we work...

A lot of the implementation for Clang modules already exists for the Google internal version of Bazel, the effort required to implement Clang modules in Bazel would be less than...

> Hello! I took a shot at implementing Clang Modules in a local bazel repo as this ticket said that everything for modules is already open-sourced. I believe I have...

That's interesting. Thanks for doing that Ryan. Would you be interested in investigating how to add support for C++20 modules to the existing native rules? It would probably require a...

The CcInfo provider was omitted on purpose. cc_shared_library is a very heavy rule that flattens nested sets, we wanted to avoid people adding a cc_shared_libraries in the middle of a...

Hi Uri, this is a nice PR, can you send it to bazelbuild/bazel? This file being repeated is an unfortunate consequence of a flag that we were never able to...

I will LGTM and merge here too.