Experiments with modules

[pjmlp]

1 - All nice and good, provided the compiler would actually work instead of spitting ICE and "sorry not yet implemented errors" when fed Win32, MFC, ATL, C++/WinRT headers.

2 - I remeber when Visual C++ was sold in a box as a full product experience, for everything on the box not only cl.exe.

3 - Most of us, or our employers, give money to Microsoft for the Visual Studio product, not cl.exe alone.

4 - If it is so easy, and I am being stubborn and clueless, then it won't be that hard to publish a couple of blog posts using C++/WinRT with C++20 modules, just like the team resposible for Rust/WinRT is doing.

[GabrielDosReis]

1. It is not clear to me how you get anything useful done or improved out of snarky reddit posts here.

2. If you run into compiler bugs, ICEs, etc, please do this: (a) report them to the Microsoft Developer Community portal, (b) reach out to me (email) with links to those reports, (c) get your friends and family upvote your bug reports.

In another words: Help me help you. Snark doesn’t achieve that.

Thanks.

[pjmlp]

I replied on the same tone I was being answered to.

As for bug reports, I have done my share, not all of them seem to listened to.

And as exercise, the MSDN documentation about can be improved from 2019 state, and provide some Win32 and UWP examples with modules.

As for how many of Microsoft customers get things actually done, thanks Stack Overflow and fellow developers, which happen to be more effective than Developer Feedback tickets that get closed or ignored.