Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commitd013bfa

Browse files
Nigel-Ecmajskeet
authored andcommitted
Update interfaces.md
Fix md-list issue
1 parent6c4a174 commitd013bfa

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

‎standard/interfaces.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -662,8 +662,9 @@ It is a compile-time error for an explicit interface member implementation to in
662662
An explicit interface method implementation inherits any type parameter constraints from the interface.
663663
664664
A *type_parameter_constraints_clause* on an explicit interface method implementation may only consist of the `class` or `struct` *primary_constraint*s applied to *type_parameter*s which are known according to the inherited constraints to be either reference or value types respectively. Any type of the form `T?` in the signature of the explicit interface method implementation, where `T` is a type parameter, is interpreted as follows:
665-
-Ifa `class`constraintisaddedfortypeparameter `T`then `T?`isanullablereferencetype;otherwise
666-
-Ifeitherthereisnoaddedconstraint,ora `struct` is added, for the type parameter `T` then `T?` is a nullable value type.
665+
666+
-Ifa `class`constraintisaddedfortypeparameter `T`then `T?`isanullablereferencetype;otherwise
667+
-Ifeitherthereisnoaddedconstraint,ora `struct` is added, for the type parameter `T` then `T?` is a nullable value type.
667668
668669
> *Example*: The following demonstrates how the rules work when type parameters are involved:
669670
>

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp