Michael Klement comments

Results 1234 comments of


                                            Michael Klement

Is it time for "PowerShell vZeroTechnicalDebt" and/or for an opt-in mechanism into new/fixed features that break backward compatibility?

@bergmeister: Valid concerns, but in the spirit of: > It's good to discuss the most valuable breaking changes please share any that you may have in mind. > slowly one...

Is it time for "PowerShell vZeroTechnicalDebt" and/or for an opt-in mechanism into new/fixed features that break backward compatibility?

Thanks, @alx9r. I think it's important to distinguish between _intrinsic_ complexity and _extrinsic_ complexity: * _Intrinsic_ complexity stems from the inherent complexity of the concepts being implemented, which in the...

Is it time for "PowerShell vZeroTechnicalDebt" and/or for an opt-in mechanism into new/fixed features that break backward compatibility?

Thanks, @HumanEquivalentUnit - that looks like a great collection. Along with the issues collected in this thread, it could form the basis for a gallery that is part of the...

Is it time for "PowerShell vZeroTechnicalDebt" and/or for an opt-in mechanism into new/fixed features that break backward compatibility?

@jszabo98's addition to the list of issues compiled here, based on #8512: `-and` and `-or` unexpectedly have the _same_ precedence, whereas in most languages (including C#) `-and` has higher precedence...

Is it time for "PowerShell vZeroTechnicalDebt" and/or for an opt-in mechanism into new/fixed features that break backward compatibility?

Just a quick note that @rjmholt has officially started a discussion about how to implement and manage breaking changes: #13129. Plus, #6817 and #10967 are more behaviors worth revisiting once...

Compare-Object with [char] instances is unexpectedly case-sensitive by default

@237dmitry: They're not _technically_ compared as strings with `-eq` (if memory serves, `.ToUpperInvariant()` is called before comparing), but the intent is clearly the same: compare `[char]`s case-INsensitively. Therefore, `Compare-Object`, which...

Parameter declarations are accepted with names that cannot be bound with named arguments, such as those that look like negative numbers

> `${foo bar}` You just need to call it correctly (I'm kidding): `` test -foo` bar hi `` As a bonus, such a parameter doesn't require an argument anymore: ``...

New syntax for invoking generic methods doesn't support overload reporting when invoked without parentheses

Thanks, @daxian-dbw: * If this assessment stands, please ensure that this limitation is documented in the new conceptual [about_Calling_Generic_Methods](https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_Calling_Generic_Methods) help topic * However, I don't see a connection between this...

Introduce a new, single-line raw string literal (single-line here-string alternative)

Thanks, @TSlivede, I've folded your suggestion into the OP. I like it, but a slight concern is that the fact that the behavior is tied to a _specific number_ of...

Introduce a new, single-line raw string literal (single-line here-string alternative)

@vexx32, yes, but note that the use of `` ` `` for escaping requires a switch to the _double-quoted_ form, because in the single-quoted one the `` ` `` would...