PowerShell does a lot of processing on behalf of its cmdlets, advanced functions etc. Sometimes this is a problem when you want to make "advanced aliases" (which in PowerShell will have to be functions). For example:

function ggl { git log graph @args }
# but could be more complex, e.g. inspect the arguments and auto-add some options.

The problem is that -- means something in Git, beyond just terminating option parsing: It separates revision arguments from file arguments. So I'd like to say,

ggl some-branch -- Some/Path

And this might work... but git never sees the -- token, so it might also not work, if there is any ambiguity. There is no way to have PowerShell not process this token so it can be passed on to sub-programs.

I deliberately make "ggl" a non-advanced function, since otherwise PowerShell would interfere even more with parsing.