Title: Member-access enumeration should not apply pipeline enumeration logic · Issue #6802 · PowerShell/PowerShell · GitHub
Open Graph Title: Member-access enumeration should not apply pipeline enumeration logic · Issue #6802 · PowerShell/PowerShell
X Title: Member-access enumeration should not apply pipeline enumeration logic · Issue #6802 · PowerShell/PowerShell
Description: Note: The behavior described below is by design and has been in place since member enumeration was introduced in v3. While it's most likely too late to change this behavior, I'm offering my observations in the context of the "PowerShell ...
Open Graph Description: Note: The behavior described below is by design and has been in place since member enumeration was introduced in v3. While it's most likely too late to change this behavior, I'm offering my observa...
X Description: Note: The behavior described below is by design and has been in place since member enumeration was introduced in v3. While it's most likely too late to change this behavior, I'm offering my...
Opengraph URL: https://github.com/PowerShell/PowerShell/issues/6802
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Member-access enumeration should not apply pipeline enumeration logic","articleBody":"Note:\r\n\r\n* The behavior described below is _by design_ and has been in place since [member enumeration](https://blogs.msdn.microsoft.com/powershell/2012/06/13/new-v3-language-features/) was introduced in v3.\r\n\r\n * While it's most likely too late to change this behavior, I'm offering my observations in the context of the \"PowerShell vZeroTechnicalDebt\" discussion - see #6745.\r\n\r\n* A request to officially document the _current_ behavior can be found [here](https://github.com/PowerShell/PowerShell-Docs/issues/2198), which arose out of the since-closed #6454.\r\n\r\n * This is a follow-up to the latter to further clarify why the existing behavior is problematic.\r\n\r\n---\r\n\r\nCurrently, `\u003cobjOrCollection>.\u003cmember>` is equivalent to \r\n`\u003cobjOrCollection> | ForEachObject { $_.\u003cmember> }`.\r\nThat is, _pipeline_ logic is applied when collecting the member values from a collection's _elements_:\r\n\r\n```powershell\r\n# A member collected from a single-element collection is unwrapped.\r\n# The following returns *scalar* 1:\r\nPS> (, @{ a = 1 }).a.GetType().Name\r\nInt32 # suggested alternative: (, 1) (single-element array)\r\n\r\n# Collecting array-valued members *concatenates* the arrays.\r\n# The following returns *flat* array 1, 2, 3, 4:\r\nPS> (@{ a = 1, 2 }, @{ a = 3, 4 }).a.Count\r\n4 # suggested alternative: (1, 2), (3, 4); a 2-element array containing the member arrays as-is\r\n```\r\n\r\nThe current behavior is problematic for the following reasons:\r\n\r\n* It is generally surprising that _pipeline_ logic is invisibly applied, given that member enumeration applies to _expression mode_ only.\r\n\r\n* Intuitively, one would expect member values to be _collected as-is_, not to be _concatenated_ if they happen to be array-valued.\r\n\r\n* The unwrapping of a single member value is especially counterintuitive in combination with `@(...)`:\r\n\r\n```powershell\r\n$objOrColl = @{ Name = 'foo' }\r\n\r\n# Ensure that $objOrColl is *array*-valued with @(...) so that -like acts as an array *filter*.\r\n# Currently the use of .Name negates the effect of @(...):\r\n@($objOrColl).Name -like 'f*'\r\nTrue # !! LHS evaluated to a *scalar* and returns a Boolean rather than the intended 'foo'\r\n```\r\n\r\nEnclosing the _entire expression_ in `@(...)` solves the problem, but that's not obvious and shouldn't be necessary: `@($objOrColl.Name) -like 'f*'`\r\n\r\n---\r\n\r\nAdditionally, in the _no-input-object_ case, member enumeration returns `$null` rather than `[System.Management.Automation.Internal.AutomationNull]::Value`, which can also lead to surprising behavior:\r\n\r\n```powershell\r\n$pids = @((Get-Process *NoSuchProcess*).Id)\r\n```\r\n\r\nThe intuitive expectation is for `$pids` to contain an _empty array_, but, because `$null` was output by the member enumeration, the actual result is `@($null)`, i.e. a single-element array containing `$null`.\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-02T13:10:19Z","url":"https://github.com/PowerShell/PowerShell/issues/6802"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:40652782-69fd-2588-856b-073be74fedbc |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | E260:FF19:2BA152:3C613F:6AFDA233 |
| html-safe-nonce | ba20b6a2183663743d6e96bd05e78eb8bafad2af3790ac551ec3685db0bee006 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJFMjYwOkZGMTk6MkJBMTUyOjNDNjEzRjo2QUZEQTIzMyIsInZpc2l0b3JfaWQiOiI0MTY3NjkwNTg0ODM3Njk0MDAzIiwicmVnaW9uX2VkZ2UiOiJpYWQiLCJyZWdpb25fcmVuZGVyIjoiaWFkIn0= |
| visitor-hmac | 6ba097770033ff7313571e33bbe776953f9dd321963080f22ac212aaef07890a |
| hovercard-subject-tag | issue:319545798 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/PowerShell/PowerShell/6802/issue_layout |
| twitter:image | https://opengraph.githubassets.com/d12b12bc9e2846be9ec1adfab5bccdf6df446fa2ce843fabd900a9d4b6f1ab1b/PowerShell/PowerShell/issues/6802 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/d12b12bc9e2846be9ec1adfab5bccdf6df446fa2ce843fabd900a9d4b6f1ab1b/PowerShell/PowerShell/issues/6802 |
| og:image:alt | Note: The behavior described below is by design and has been in place since member enumeration was introduced in v3. While it's most likely too late to change this behavior, I'm offering my observa... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | mklement0 |
| hostname | github.com |
| expected-hostname | github.com |
| None | bc86424ef34a73b386237872800e922d149d65ba907f63d6f150a2dcb8433bea |
| turbo-cache-control | no-preview |
| go-import | github.com/PowerShell/PowerShell git https://github.com/PowerShell/PowerShell.git |
| octolytics-dimension-user_id | 11524380 |
| octolytics-dimension-user_login | PowerShell |
| octolytics-dimension-repository_id | 49609581 |
| octolytics-dimension-repository_nwo | PowerShell/PowerShell |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 49609581 |
| octolytics-dimension-repository_network_root_nwo | PowerShell/PowerShell |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 927a6c5ab1c32b38830f1b9d3050c0b9e9aa92e1 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width