Including Enums/Classes in standard Import-Module cmdlet

[NoUselessTech]

While classes and Enums aren't used by most PowerShell users in their day to day, I happen to like them. Having done development in other languages, these are crucial features in my opinion. As someone who does write modules from time to time, it would be nice to have classes and Enums that are properly imported under standard import conditions rather than with the "using" method.

Unlike many who might just whine about this, I am considering making a code contribution to this platform language. There are a few pieces of information I lack that I'm hoping to get from the community:

• Did I just miss this feature being on the roadmap?
• Are there reasons why classes and enums are intentionally left out of the standard module import path?
• Where would be a good starting point for looking through the code and enhancing the import-module cmdlet?

Thanks in advance for your input!