Repository navigation
Add extensibility point for LINQ expression tree compilation - #647
Merged
Merged
Conversation
3 tasks done
stakx
force-pushed
the
expression-compiler
branch
from
July 26, 2018 21:17
bcbb787 to
90dd72a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As contemplated in #504 (comment).
This would enable users to configure Moq to use their own LINQ expression tree compilation strategies, such as:
It would seem like a nice feature to merge, since it enables some new options and is trivial to implement.