Add documentation for the PInvoke probe algorithm. #28729
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
|
/cc @gewarren |
jkoritzinsky
approved these changes
Mar 18, 2022
gewarren
approved these changes
Mar 18, 2022
Co-authored-by: Genevieve Warren <24882762+gewarren@users.noreply.github.com>
lambdageek
approved these changes
Mar 18, 2022
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.
Summary
Documentation for PInvoke probe algorithm. The documentation here represents only the guarantees for the probing. There are other niche scenarios that may change over time and thus is not exhaustive. It also only documents the runtime algorithm and does not dictate further logic applied by the underlying platform.
See
LoadNativeLibraryBySearch().Fixes dotnet/runtime#4596
/cc @dotnet/interop-contrib