Formulate a questionnaire to start the conversation with tooling providers

[ruoso]

I'll use this issue to refine a questionnaire that will be used to jump start the conversations with tooling providers on what the support for a project that does import std is, where that development needs to go, and perhaps more importantly, what is needed from the ecosystem for that support to become fully supported.

Questionnaire Template

1. What is the current level of support for "a project that does import std" in this tool today?

2. Is there any impediment, besides funding, to drive the completion of the support for that feature?

3. If applicable, what is the plan for your tool to support compilers that support multiple different standard libraries?

4. If applicable, what is the plan for your tool to support different compilers?

5. If applicable, what is the plan for your tool to support different translation units in the same project requiring different BMIs (Built Module Interfaces) for the std module?

6. What would you need from other parts of the ecosystem to make the implementation of "a project that does import std" viable in your tool?

[ruoso]

I will edit the description of the issue as feedback is provided in comments here. Please let me know if the questions are clear and if you think they're starting points for input. Also, let me know if you have any additional questions that you think would be helpful.

[ChuanqiXu9]

If applicable, what is the plan for compilers that support multiple different standard libraries?

What is the target for the question? Even if for compilers (clang or gcc or ...), it reads odd. Since there are not compilers for the different compiler communities.

[ruoso]

If applicable, what is the plan for compilers that support multiple different standard libraries?

What is the target for the question?

The target is for things at a higher level, such as build systems, package managers and static analysis tools.

[ChuanqiXu9]

If applicable, what is the plan for compilers that support multiple different standard libraries?

What is the target for the question?

The target is for things at a higher level, such as build systems, package managers and static analysis tools.

Oh, I see. You want to ask: what do you want to do if there a compiler that supports multiple different standard modules? Then it makes sense.

[ruoso]

I updated the wording a bit to make that more clear.