-
Notifications
You must be signed in to change notification settings - Fork 933
NH-3964 - obsolete Linq.ReflectionHelper in favor of Util.ReflectHelper. #586
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NH-3964 - obsolete Linq.ReflectionHelper in favor of Util.ReflectHelper. #586
Conversation
|
Snapshot dependency failure for failed build: looks like a Team City infrastructure failure, doesn't it? I should probably trigger a later rebuild with a rebase. |
src/NHibernate/Util/ReflectHelper.cs
Outdated
@@ -565,7 +651,7 @@ internal static object GetConstantValue(string qualifiedName, ISessionFactoryImp | |||
return null; | |||
} | |||
|
|||
[Obsolete("Please use Linq.ReflectionHelper instead")] | |||
[Obsolete("Please use Linq.ReflectHelper instead")] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, search&replace does not make it for this obsolete reason. I would fix it tomorrow for triggering another build by the way.
0ffd5ea
to
0c25d3e
Compare
Amended for updating a doc example referencing |
0c25d3e
to
535d7a2
Compare
Found two additional method reflection which are cacheable and were not. Now cached. And rebased. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Follow up of NH-3964 and its first PR #574 .
Methods are just moved to ReflectHelper, without changing them.
Trying to use
is requiring as many overloads as function arguments counts
Then type inference is sometime inferior:
Instead of
And handling instance methods are requiring a
Func<Func<>>
with a non-null instance:So well, even though some "brute force" runtime performance comparison show it is "better", I do not think it is worth all the required changes and additional code for using them.