On Sun, Feb 16, 2025 at 22:59:45 +0100, Ben Boeckel wrote: > But we are finally at a point where named modules can be experimented > with. The timeline has been (roughly): > > - 2019 Feb: pushing to get dependency scanning possible (I have patches > to CMake and GCC to proof-of-concept at the Kona meeting) > - 2019 Mar: CMake uses P1689R2 for its Fortran scanning/dependency > computations. The implementation is updated for further revision > updates as time goes on.
Sorry, I missed some entries here: - 2019 Apr: Patches to `ninja` land to support `dyndep` (needed for accurate C++ dependency scanning) - 2020 Jan: `ninja` 1.10 releases with `dyndep` support > - 2020-2022: hammering out P1689 details. As of P1689R5 it is in a place > where everyone is happy. Alas, my allocations did not align with > faster progress here. > - 2022 Jun: experimental support for named modules lands in CMake 3.25. > Community and toolchain implementers experiment with my GCC patches > and report issues. > - 2023 Sep: my P1689R5 patches land in GCC > - 2023 Oct: CMake 3.28 releases with named imports as a non-experimental > feature > - 2022 Nov: VS 17.4 releases with P1689 support > - 2023 Feb: clang-scan-deps learns to write P1689R5 > - 2024 Apr: Support for clang/libc++ and MSVC/STL `import std;` lands in > CMake `master` > - 2024 Jul: Experimental support for `import std;` in CMake 3.30. > - 2024 Nov: Support for GCC's `import std;` lands --Ben
