René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Tab completion attempt at `@` returns no result, `@?` crashes PSReadLine, or provides invalid result","articleBody":"# Steps to reproduce\r\n\r\nAttempt tab completion/intellisense of splats:\r\n\r\n```PowerShell\r\n@\u003cCTRL SPACE\u003e\r\n@?\u003cCTRL SPACE\u003e # CRASH PSReadLine\r\n@?\u003cTAB\u003e # results in `@{$}` which is unusable as it tries to make a hashtable\r\n```\r\n`tabexpansion2` also provides no results for ( `'@' 1`).\r\n\r\n# Environment data\r\n\r\nBelieved to occur in all versions, tested in 7.0.0-preview2 and Windows PowerShell on Win 10 Insiders.\r\n\r\n# Insights\r\n\r\nI believe the example of `@?` crashing PSReadLine is related to the expansion to `@{$}`, and while it probably shows a bug in PSReadLine, PR #10226 would fix the completion (though its likely to be a new problem with the new @@ splats being worked on.\r\n\r\nI am not sure yet why `@` alone cannot start a completion, I'm trying to consider what the completion code can do about offering completions that wont work.  I don't think there is currently a syntax that works for splatting variables with complex names, and I didn't see it in the RFC for Enhanced Splatting.","author":{"url":"https://github.com/msftrncs","@type":"Person","name":"msftrncs"},"datePublished":"2019-07-29T02:45:14.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/10243/PowerShell/issues/10243"}