Klaus Frank

Hi, as I just come across the "formatting and mounting bricks" wiki page and was kinda confused by it I'd like to share some of the problems and questions I...

Any update on this? Just noticed, that it also applies for explicitly defined arrays, which is quite irritating: ```powershell Set-StrictMode -Version 7 [pscustomobject[]]$a = $null # e.g. returned by something...

Is that still experimental? 7.0.3 returns only this: `You must provide a value expression following the '?' operator.` Edit: Yes it is and it's called PSNullConditionalOperators

The best workaround I found so far is using `Measure-Object`. That way, it'll also work with older versions of PowerShell (mainly the windows one, for cases where it is needed...

Is this still open? Just hit that bug again in 7.3.7, but in a kinda "new and interesting way". What works: ``` Set-StrictMode -Version latest [string[]]$a = @() $a.Count ```...

Thanks @iRon7, yea the `Resolution-No Activity` thingy of the bot is annoying. I just wasted valuable time c'n'p-ing a dummy message into a lot of tickets here. If I have...

Just fixed a bug in a script that used: ``` if ('Debug' -in $PSBoundParameters.Keys) {} ``` This needs to be fixed or at least we need warnings from psscriptanalyzer (and...

@Jaykul That wasn't my code I found that "gem" in the code of coworkers... Regardless of that the Switch shouldn't be a nullable bool, but just a bool. And `-Debug:$false`...

You raise a good point, we definitely need a kind of versioning for the language itself. And better sooner than later. Because it would have to be in widespread use...

Another thought. If we say switches from CommonParameters are actually intended to be the way they currently are with three states `$null`, `$true`, `$false`, I.E. a nullable switches, can we...