-
Notifications
You must be signed in to change notification settings - Fork 8.4k
Expression interpreter has received a lot of improvements in CoreFx #2230
Copy link
Copy link
Closed
Labels
Issue-Enhancementthe issue is more of a feature request than a bugthe issue is more of a feature request than a bugResolution-No ActivityIssue has had no activity for 6 months or moreIssue has had no activity for 6 months or moreUp-for-GrabsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsWG-Enginecore PowerShell engine, interpreter, and runtimecore PowerShell engine, interpreter, and runtimeWG-Engine-Performancecore PowerShell engine, interpreter, and runtime performancecore PowerShell engine, interpreter, and runtime performance
Metadata
Metadata
Assignees
Labels
Issue-Enhancementthe issue is more of a feature request than a bugthe issue is more of a feature request than a bugResolution-No ActivityIssue has had no activity for 6 months or moreIssue has had no activity for 6 months or moreUp-for-GrabsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsWG-Enginecore PowerShell engine, interpreter, and runtimecore PowerShell engine, interpreter, and runtimeWG-Engine-Performancecore PowerShell engine, interpreter, and runtime performancecore PowerShell engine, interpreter, and runtime performance
Type
Fields
Give feedbackNo fields configured for issues without a type.
As a heads-up, the expression interpreter under
src\System.Management.Automation\engine\interpreterseems to be a clone from the original code in the DLR. Many improvements to it were made in the CoreFx repo at http://github.com/dotnet/corefx. It'd be good to consider either porting these changes or eliminating the copy altogether once theCompile(bool preferInterpretation)overload is available on all platforms by PowerShell. Note that the regularCompile()overload will be available on all platforms that supportSystem.Linq.Expressionsand will use the interpreter in case the compiler is not available.