WSL API missing function to enumerate installed distributions

[riverar]

Consuming the WSL API requires developers to populate the distribution name parameter for most functions. There is no API to retrieve a list of valid distribution names, however, and none of the APIs support a nullptr input to signify the user's default distribution should be used, as general Win32 programming patterns would nudge you towards.

How are developers meant to consume these APIs? The dev story seems incomplete.

Related: #3515 #3543

[Biswa96]

The Microsoft-ish suggestion is to parse the output of wsl.exe -l -v command. You can use the other way, you-know-what.

[riverar]

Ha, parsing executable output is not a solution.

[therealkenc]

Trick to turn this tag feature, contrast death by tag discussion ref #3515, is providing the use case for your AP change request. [With no implication there is no use case. But that's how the dupe died two weeks after it was opened.]

[riverar]

@therealkenc no idea what your comment means, looks like a typo?

[therealkenc]

This submission is spiritually similar to #3515. #3515 was a discussion thread (label/tag 'discussion') that ran course and was closed. The hope is some use cases for the implied API enhancement are provided, thumbs up on the OP appear, and this one (which to be clear is entirely sensible) has a better chance than #3515. Question / observational commentary ("How are developers meant to consume these APIs? The dev story seems incomplete"), on a statistical basis anyway, usually end up chirping crickets.

[riverar]

Thanks for clarifying. (I fundamentally have an issue with your ability to label/close issues using an imaginary rubric and without Microsoft involvement.)

In this particular case, Microsoft is providing an API that is useless without the enumeration capability and I'd continue to argue this is a bug.