Remove most references to the CLI (#1370)

* Remove most references to CLI

* Remove most CLI references

* Remove most CLI references

* Remove most CLI references

* Remove most CLI references

* Update standard/standard-library.md

Co-authored-by: Kalle Olavi Niemitalo <kon@iki.fi>

* Update standard/standard-library.md

Co-authored-by: Nigel-Ecma <6654683+Nigel-Ecma@users.noreply.github.com>

* Update standard/standard-library.md

---------

Co-authored-by: Kalle Olavi Niemitalo <kon@iki.fi>
Co-authored-by: Jon Skeet <skeet@pobox.com>
Co-authored-by: Nigel-Ecma <6654683+Nigel-Ecma@users.noreply.github.com>

Author: 4 people

standard/attributes.md

@@ -483,35 +483,6 @@ Using the terms defined in [§22.4.2](attributes.md#2242-compilation-of-an-attri
   - The result is `O`, an instance of the attribute class `T` that has been initialized with the *positional_argument_list* `P` and the *named_argument_list* `N`.
 
 > *Note*: The format for storing `T`, `C`, `P`, `N` (and associating it with `E`) in `A` and the mechanism to specify `E` and retrieve `T`, `C`, `P`, `N` from `A` (and hence how an attribute instance is obtained at runtime) is beyond the scope of this specification. *end note*
-<!-- markdownlint-disable MD028 -->
-
-<!-- markdownlint-enable MD028 -->
-> *Example*: In an implementation of the CLI, the `Help` attribute instances in the assembly created by compiling the example program in [§22.2.3](attributes.md#2223-positional-and-named-parameters) can be retrieved with the following program:
->
-> <!-- Example: {template:"standalone-console", name:"RuntimeAttributeInstanceRetrieval", expectedOutput:["Type : Microsoft.CodeAnalysis.EmbeddedAttribute", "Type : System.Runtime.CompilerServices.NullableAttribute", "Type : System.Runtime.CompilerServices.NullableContextAttribute", "Type : HelpAttribute", "Type : InterrogateHelpUrls"], additionalFiles:["HelpAttribute.cs"], executionArgs:["RuntimeAttributeInstanceRetrieval"]} -->
-> <!-- Maintenance Note: The current expectedOutput is based on MS-specific implementation details. -->
-> ```csharp
-> public sealed class InterrogateHelpUrls
-> {
->     public static void Main(string[] args)
->     {
->         Type helpType = typeof(HelpAttribute);
->         string assemblyName = args[0];
->         foreach (Type t in Assembly.Load(assemblyName).GetTypes()) 
->         {
->             Console.WriteLine($"Type : {t}");
->             var attributes = t.GetCustomAttributes(helpType, false);
->             var helpers = (HelpAttribute[]) attributes;
->             foreach (var helper in helpers)
->             {
->                 Console.WriteLine($"\tUrl : {helper.Url}");
->             }
->         }
->     }
-> }
-> ```
->
-> *end example*
 
 ## 22.5 Reserved attributes
 

standard/basic-concepts.md

@@ -564,7 +564,7 @@ Signatures are the enabling mechanism for ***overloading*** of members in classe
 
 Although `in`, `out`, and `ref` parameter modifiers are considered part of a signature, members declared in a single type cannot differ in signature solely by `in`, `out`, and `ref`. A compile-time error occurs if two members are declared in the same type with signatures that would be the same if all parameters in both methods with `out` or `in` modifiers were changed to `ref` modifiers. For other purposes of signature matching (e.g., hiding or overriding), `in`, `out`, and `ref` are considered part of the signature and do not match each other.
 
-> *Note*: This restriction is to allow C# programs to be easily translated to run on the Common Language Infrastructure (CLI), which does not provide a way to define methods that differ solely in `in`, `out`, and `ref`. *end note*
+> *Note*: This restriction is to allow C# programs to be easily translated to run on a platform that does not provide a way to define methods that differ solely in `in`, `out`, and `ref`. *end note*
 
 The types `object` and `dynamic` are not distinguished when comparing signatures. Therefore members declared in a single type whose signatures differ only by replacing `object` with `dynamic` are not allowed.
 

standard/introduction.md

@@ -2,7 +2,7 @@
 
 This specification is based on a submission from Hewlett-Packard, Intel, and Microsoft, that described a language called C#, which was developed within Microsoft. The principal inventors of this language were Anders Hejlsberg, Scott Wiltamuth, and Peter Golde. The first widely distributed implementation of C# was released by Microsoft in July 2000, as part of its .NET Framework initiative.
 
-Ecma Technical Committee 39 (TC39) \[later renamed to TC49\] Task Group 2 (TG2) was formed in September 2000, to produce a standard for C#. Another Task Group, TG3, was also formed at that time to produce a standard for a library and execution environment called Common Language Infrastructure (CLI). (CLI is based on a subset of the .NET Framework.) Although Microsoft’s implementation of C# relies on CLI for library and run-time support, other implementations of C# need not, provided they support the features and API required by this C# Standard (see [Annex C](standard-library.md#annex-c-standard-library)).
+Ecma Technical Committee 39 (TC39) \[later renamed to TC49\] Task Group 2 (TG2) was formed in September 2000, to produce a standard for C#. Another Task Group, TG3, was also formed at that time to produce a standard for a library and execution environment called Common Language Infrastructure (CLI). (CLI is based on a subset of the .NET Framework.) Although Microsoft’s implementation of C# relies on CLI for library and run-time support, other conforming implementations of C# need not, provided they support the features required by this C# Standard (see [Annex C](standard-library.md#annex-c-standard-library)).
 
 As the definition of C# evolved, the goals used in its design were as follows:
 

standard/portability-issues.md

@@ -72,6 +72,6 @@ A conforming implementation is required to document its choice of behavior in ea
 ## B.5 Other issues
 
 1. The exact results of floating-point expression evaluation can vary from one implementation to another, because an implementation is permitted to evaluate such expressions using a greater range and/or precision than is required ([§8.3.7](types.md#837-floating-point-types)).
-1. The CLI reserves certain signatures for compatibility with other programming languages ([§15.3.10](classes.md#15310-reserved-member-names)).
+1. Certain signatures are reserved for compatibility with other programming languages ([§15.3.10](classes.md#15310-reserved-member-names)).
 
 **End of informative text.**

standard/standard-library.md

@@ -2,7 +2,9 @@
 
 ## C.1 General
 
-A conforming C# implementation shall provide a minimum set of types having specific semantics. These types and their members are listed here, in alphabetical order by namespace and type. For a formal definition of these types and their members, refer to ISO/IEC 23271:2012 *Common Language Infrastructure (CLI), Partition IV; Base Class Library (BCL), Extended Numerics Library, and Extended Array Library*, which are included by reference in this specification.
+A conforming C# implementation shall provide a minimum set of types having specific semantics. These types and their members are listed here, in alphabetical order by namespace and type. For a formal definition of the types and their members identified in ([§C.2](standard-library.md#c2-standard-library-types-defined-in-isoiec-23271)), refer to ISO/IEC 23271:2012 *Common Language Infrastructure (CLI), Partition IV; Base Class Library (BCL), Extended Numerics Library, and Extended Array Library*, which are included by reference in this specification. For a list of types and their members required beyond those identified in §C.2, see [§C.3](standard-library.md#c3-standard-library-types-not-defined-in-isoiec-23271).
+
+> *Note*: The adoption of a subset of the CLI’s library API does not create a dependency on the CLI itself; a conforming implementation need not be built upon, or target, the CLI.
 
 **This text is informative.**