Mathias R. Jessen

WG-Engine reviewed this issue yesterday, and we generally agree the full extent of the originating statement should be made part of the public API, but that the `Line` property should...

@rjmholt I believe https://github.com/PowerShell/PowerShell/issues/8302 (classes don't produce valid interface property methods) should be filed under "Other bugs"

@rjmholt well, we already mark all generated methods `virtual`, allowing class definitions to inherit existing interfaces: ```powershell class PleaseDisposeOfMe : IDisposable { [void]Dispose(){ } } ``` but since we never...

Engine WG discussed this issue today ### Points raised by the committee We fully agree that SMA.dll should offer better insights into module path preferences through its public API surface...

Very cool, thanks for reviving this topic @MartinGC94!

> How should conflicting type aliases work? Consider the following example: > > ``` > using namespace System.Timers > using type Timer = string > [Timer] #What type is this?...

> Not sure how much help #12412 will be in the end for this specific PR, but I agree it would be better to get that in place first, so...

Right now we don't handle duplicates at runtime, we simply seed a runtime conflict: ``` using namespace System.Collections.Specialized using namespace System.Collections.Specialized [BitVector32] ``` Results in the following runtime error: ```...

@rkeithhill yes, thanks for the kind reminder! 😄

I'm aware that `` ` `` isn't a wildcard char in DOS, but PowerShell isn't DOS. If it doesn't need escaping, then you'd expect `` 'a`b' -like 'a`b' `` to...