Skip to content

Tweak example annotation #1069

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

Merged
merged 2 commits into from
Mar 30, 2024
Merged
Show file tree
Hide file tree
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
4 changes: 2 additions & 2 deletions standard/classes.md
Original file line number Diff line number Diff line change
Expand Up @@ -1596,7 +1596,7 @@ Constants and readonly fields have different binary versioning semantics. When a

> *Example*: Consider an application that consists of two separate programs:
>
> <!-- RequiresSeparateProjects$Example: {template:"standalone-lib-without-using", name:"VersioningOfConstantsAndStaticReadonlyFields1"} -->
> <!-- Incomplete$Example: {template:"standalone-lib-without-using", name:"VersioningOfConstantsAndStaticReadonlyFields1"} -->
> ```csharp
> namespace Program1
> {
Expand All @@ -1609,7 +1609,7 @@ Constants and readonly fields have different binary versioning semantics. When a
>
> and
>
> <!-- RequiresSeparateProjects$Example: {template:"standalone-console", name:"VersioningOfConstantsAndStaticReadonlyFields2", expectedOutput:["x", "x", "x"], expectedErrors:["x","x"], expectedWarnings:["x","x"]} -->
> <!-- Incomplete$Example: {template:"standalone-console", name:"VersioningOfConstantsAndStaticReadonlyFields2", expectedOutput:["x", "x", "x"], expectedErrors:["x","x"], expectedWarnings:["x","x"]} -->
> ```csharp
> namespace Program2
> {
Expand Down
4 changes: 2 additions & 2 deletions standard/unsafe-code.md
Original file line number Diff line number Diff line change
Expand Up @@ -183,7 +183,7 @@ The default value ([§9.3](variables.md#93-default-values)) for any pointer type
> *Note*: Although pointers can be passed as `in`, `ref` or `out` parameters, doing so can cause undefined behavior, since the pointer might well be set to point to a local variable that no longer exists when the called method returns, or the fixed object to which it used to point, is no longer fixed. For example:
>
> <!-- Example: {template:"standalone-console-without-using", name:"PointerTypes1", replaceEllipsis:true} -->
> <!-- Note: the behavior of this example is undefined. -->
> <!-- Maintenance Note: the behavior of this example is undefined. -->
> ```csharp
> class Test
> {
Expand Down Expand Up @@ -296,7 +296,7 @@ When one pointer type is converted to another, if the resulting pointer is not c
> *Example*: Consider the following case in which a variable having one type is accessed via a pointer to a different type:
>
> <!-- Example: {template:"standalone-console-without-using", name:"PointerConversions1", expectedWarnings:["CS8321"]} -->
> <!-- Note: the behavior of this example is undefined. -->
> <!-- Maintenance Note: the behavior of this example is undefined. -->
> ```csharp
> unsafe static void M()
> {
Expand Down