Staffan Gustafsson
Staffan Gustafsson
There is a substantial difference in the underlying model between the *nix systems, which start new processes for each part of the pipeline, and PowerShell, which runs the pipeline on...
Looking at this with a native debugger: ``` 0:022> k # Child-SP RetAddr Call Site 00 00000045`cd3c8b18 00007fff`76556c5d coreclr!isJumpRel64 [D:\a\_work\1\s\src\coreclr\vm\amd64\cgenamd64.cpp @ 395] 01 00000045`cd3c8b20 00007fff`76556c27 coreclr!Precode::IsPointingTo+0x11 [D:\a\_work\1\s\src\coreclr\vm\precode.h @ 494] 02...
WG-Engine reviewed this and agrees that it's a bug, and are glad to see a PR in progress.
Currently, that's the case, but it's not a law of nature that it has to be so. It would be nice to be able to build from VS without hassle.
Would it be OK to add a reference to System.CommandLine?
On the other hand, others would run into issues using diffferent version of System.CommandLine. It may not be the worst to have it in a dependable way, and it would...
What are you trying to accomplish? Why not `{ [Environment]::GetEnvironmentVariable( $args[0] ) }` or `{ param([string] $name) [Environment]::GetEnvironmentVariable( $name ) }`
I think it is more the question of what the gain is. Seems like ```{$delegate.invoke()}``` would accomplish the same thing. @poizan42 Do you mean we should add this as a...