Uh oh!
There was an error while loading. Please reload this page.
Make LambdaCompiler prefer interpretation to compilation on iOS - #54970
Make LambdaCompiler prefer interpretation to compilation on iOS#54970steveisok merged 20 commits into
Conversation
ghost
commented
Jun 30, 2021
Tagging subscribers to this area: @cston Issue DetailsThis is an attempt to address #47112 based on Egor's suggestion.
|
Uh oh!
There was an error while loading. Please reload this page.
Co-authored-by: Stephen Toub <stoub@microsoft.com>
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
MaximLipnin
commented
Jul 1, 2021
Actually, |
Can you file separate issues for each and tag them with |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
…led as IsInterpreting only
This is an attempt to address #47112 based on Egor's suggestion.
The changes:
IsInterpretingMSBuild property to 'true' in case of iOS;System.Linq.Expressions.ExpressionCreatorclass internal static in order not to introduce new public type; otherwise it throwsType 'System.Linq.Expressions.ExpressionCreator<TDelegate>' does not exist in the reference but it does exist in the implementation.PlatformDetection.IsLinqExpressionsBuiltWithIsInterpretingOnlywhich checks whether theSystem.Linq.Expressionsis built withIsInterpretingproperty set totrue. To do so, it uses reflection to verify theExpression.Acceptmethod doesn't exist.