René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Allow Measure-Object to accept ad-hoc script-block arguments in lieu of property names","articleBody":"\u003csup\u003eThis issue arose out of #6837.\u003c/sup\u003e\r\n\r\nMotivation:\r\n\r\n`Sort-Object`'s `-Property` not only supports property _names_ (the typical case), but also _script blocks_ that are evaluated for each input object and thereby enable sorting criteria _derived_ from properties, which is a powerful feature (also found, in essence, in `Select-Object`); e.g.:\r\n\r\n```powershell\r\n# Sort by only the numerical part of the input, via a script-block parameter argument.\r\nPS\u003e 'z1', 'a0', 'b10' | Sort-Object -Property { [int] $_.Substring(1) }\r\na0\r\nz1\r\nb10\r\n```\r\n\r\nSuggestion:\r\n\r\nIt would be handy if `Measure-Object` supported analogous use; e.g.:\r\n\r\n```powershell\r\n# Count the  odd numbers in the input.\r\nPS\u003e 1, 2, 3 | Measure-Object -Sum -Property { $_ % 2 }  # wishful thinking\r\n2\r\n```\r\n\r\nTo that end:\r\n\r\n* The `-Property` parameter's data type would have to change from`[string[]]` to `[object[]]`\r\n* In the event of a script block getting passed, it would have to be evaluated for each input object and used in lieu of a simple property access on the input object.\r\n\r\n\r\nEnvironment data\r\n----------------\r\n\r\nWritten as of:\r\n\r\n```powershell\r\nPowerShell Core v6.0.2\r\n```\r\n","author":{"url":"https://github.com/mklement0","@type":"Person","name":"mklement0"},"datePublished":"2018-05-11T13:56:44.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":8},"url":"https://github.com/6855/PowerShell/issues/6855"}