Bruce,

The method being modified is also used by VisitContinueStatement and VisitReturnStatement, which I believe should still throw the error when present in a switch statement rather than being "fixed" along with Break.

@TimCurwick When it's a return statement, the caller will pass in null for the label parameter, and thus it won't be affected by the changes in this PR at all.

For a continue statement, it's fine. Use continue in a switch clause will continue on the next item in the collection, or exit the switch statement if no item is available. That should continue to work in a finally block. See the example below:

switch -wildcard ( 'Hello World', 'World' )
{
     '*hello*'
     {
         "process hello in '$_'"
     }
     '*world*'
     {
          "process world in '$_'"
     }
}

> process hello in 'Hello World'
> process world in 'Hello World'
> process world in 'World'

switch -wildcard ( 'Hello World', 'World' )
{
    '*hello*'
    {
         "process hello in '$_'"
         continue
    }
    '*world*'
    {
         "process world in '$_'"
    }
}

> process hello in 'Hello World'
> process world in 'World'

Ah. Of course. Thank you.

Though that does point to a problem with help topic about_Continue, which says, "In a script, the Continue statement immediately returns the program flow to the top of the innermost loop that is controlled by a For, Foreach, or While statement."

@TimCurwick That looks like a doc bug. Can you please open an issue in https://github.com/powershell/powershell-docs? Thank you!