René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Why is [pscustomobject] the same as [psobject], even though a distinct [System.Management.Automation.PSCustomObject] type exists?","articleBody":"Surprisingly, `[pscustomobject]` is the same as  `[psobject]`: both these type accelerators point to type `[System.Management.Automation.PSObject]`, even though there _is_ a distinct `[System.Management.Automation.PSCustomObject]` type.\r\n\r\nMostly, this conflation goes unnoticed (and has come up before - see #2295), but:\r\n\r\n* what is the rationale for it?\r\n\r\n* it makes for surprising behavior on occasion - see below.\r\n\r\n```powershell\r\n# Even though their names strongly suggest identity, they are different types.\r\n\u003e [pscustomobject] -eq [System.Management.Automation.PSCustomObject]\r\nFalse\r\n\r\n# Any object returned by a *command* (as opposed to an expression)\r\n# returns $True for -is [psobject], and therefore also [pscustomobject]\r\n\u003e (Get-Item /) -is [pscustomobject]\r\nTrue\r\n\r\n# Casting anything other than a hashtable literal to [psobject] is a no-op, \r\n# and therefore also with [pscustomobject]\r\n\u003e ([pscustomobject] 666).GetType().Name\r\nInt32\r\n```\r\n\r\n\r\nEnvironment data\r\n----------------\r\n\r\n```powershell\r\nPowerShell Core v6.0.0-beta.4\r\n```\r\n","author":{"url":"https://github.com/mklement0","@type":"Person","name":"mklement0"},"datePublished":"2017-07-26T04:33:34.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":13},"url":"https://github.com/4344/PowerShell/issues/4344"}