Skip to content
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

Add example to doc for UnsafeAccessor #88040

Merged
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -56,6 +56,20 @@ public enum UnsafeAccessorKind
/// Return type is considered for the signature match. modreqs and modopts are initially not considered for
/// the signature match. However, if an ambiguity exists ignoring modreqs and modopts, a precise match
/// is attempted. If an ambiguity still exists <see cref="System.Reflection.AmbiguousMatchException" /> is thrown.
///
/// By default, the attributed method's name dictates the name of the method/field. This can cause confusion
/// in some cases since language abstractions, like C# local functions, generate mangled IL names. The
/// solution to this is to use the <code>nameof</code> mechanism and define the <see cref="Name"/> property.
///
/// <code>
/// public void Method(Class c)
/// {
/// PrivateMethod(c);
///
/// [UnsafeAccessor(UnsafeAccessorKind.Method, Name = nameof(PrivateMethod))]
/// extern static void PrivateMethod(Class c);
/// }
/// </code>
/// </remarks>
[AttributeUsage(AttributeTargets.Method, AllowMultiple = false, Inherited = false)]
public sealed class UnsafeAccessorAttribute : Attribute
Expand Down
Loading