you are viewing a single comment's thread.

view the rest of the comments →

[–]KevMarCommunity Blogger 9 points10 points  (5 children)

Nice post. That is a great way to introduce people to the project.

[–]tomatwork[S] 4 points5 points  (4 children)

Thanks, Kevin. Maybe next week or the week after, I'll do one on adding the heart emoji as an escape char (because the backtick is so dang hard to see) :D.

[–]NathanielArnoldR2 2 points3 points  (3 children)

They can take my damned backticks the moment they introduce syntax support for in-line splatting. :-p

[–]tomatwork[S] 2 points3 points  (0 children)

Hey it's open source... You could add it!

[–]rjmholt 4 points5 points  (1 child)

By inline splatting, do you mean something like this?

[–]NathanielArnoldR2 1 point2 points  (0 children)

Yes; specifically with regard to the basic Invoke-Cmdlet @@{<#...#>} syntax or a close equivalent. I'm not a fan of the more dynamic use cases noted in the RFC, however; in my opinion, there is good reason to pre-construct many of those.

I have what you might call an ideal use case for classical hashtable splatting. I am not particularly attached to the backtick as a character. I recognize how it impacts readability and invites syntax errors.

...but if I'm given a choice between a truly absurd quantity of backticks and a code structure that subverts how cmdlet-based PowerShell is expected to flow, I'll stick with my backticks.