Date: Tue, 12 Dec 2023 11:22:14 +0200
Michael Spencer via SG15 <sg15_at_[hidden]> writes:
> This was the best time for those most involved in the discussion, but
> unfortunately I wasn't able to find a time when Boris was also available.
That's ok, I believe I've expressed my suggestions in the libc++ issue
you linked to earlier. Just to summarize (and add another point):
1. Think of the downstream packagers (Debian, Fedora, etc).
2. Make it easy and fast for build systems to find the std module
location (e.g., reuse mechanisms such as -print-search-dirs
that build systems already likely use).
3. Don't make this depend on solving "package management" or other
hypothetical requirements.
We have experience with two of the three major standard library
implementations (MS STL and libc++) and making the std module
source file available in a way similar to headers does the job.
> This was the best time for those most involved in the discussion, but
> unfortunately I wasn't able to find a time when Boris was also available.
That's ok, I believe I've expressed my suggestions in the libc++ issue
you linked to earlier. Just to summarize (and add another point):
1. Think of the downstream packagers (Debian, Fedora, etc).
2. Make it easy and fast for build systems to find the std module
location (e.g., reuse mechanisms such as -print-search-dirs
that build systems already likely use).
3. Don't make this depend on solving "package management" or other
hypothetical requirements.
We have experience with two of the three major standard library
implementations (MS STL and libc++) and making the std module
source file available in a way similar to headers does the job.
Received on 2023-12-12 09:22:07