Fixes corrupted weaving attributes #47
Merged
Conversation
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
AlexUstinov
approved these changes
Jul 23, 2020
alex-kulakov
pushed a commit
that referenced
this pull request
Nov 9, 2021
…FieldAccessorResolver (#47) * Optimization: allocate immutable Expression objects statically; ValueFieldAccessorResolver * Further improve ValueFieldAccessorResolver * Revert converting ValueFieldAccessorResolver to Dictionary * Move Fun<,> to WellKnownTypes.FuncOfTArgTResultType
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes issue #46.
When a processible project used to have a reference to
Xtensive.Ormbut during compilation the reference has lost thenWeaveradds the reference back to target assembly to prevent weaving attributes from being declared as owned by target assembly.