You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: xml/System.Text.RegularExpressions/Regex.xml
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -1194,7 +1194,7 @@ On .NET Core, calls to the `Regex.CompileToAssembly` method throw a <xref:System
1194
1194
> [!NOTE]
1195
1195
> If a regular expression pattern includes either the number sign (#) or literal white-space characters, they must be escaped if input text is parsed with the <xref:System.Text.RegularExpressions.RegexOptions.IgnorePatternWhitespace?displayProperty=nameWithType> option enabled.
1196
1196
1197
-
While the <xref:System.Text.RegularExpressions.Regex.Escape%2A> method escapes the straight opening bracket ([) and opening brace ({) characters, it does not escape their corresponding closing characters (] and }). In most cases, escaping these is not necessary. If a closing bracket or brace is not preceded by its corresponding opening character, the regular expression engine interprets it literally. If an opening braket or brace is interpreted as a metacharacter, the regular expression engine interprets the first corresponding closing character as a metacharacter. If this is not the desired behavior, the closing bracket or brace should be escaped by explicitly prepending the backslash (\\) character. For an illustration, see the Example section.
1197
+
While the <xref:System.Text.RegularExpressions.Regex.Escape%2A> method escapes the straight opening bracket ([) and opening brace ({) characters, it does not escape their corresponding closing characters (] and }). In most cases, escaping these is not necessary. If a closing bracket or brace is not preceded by its corresponding opening character, the regular expression engine interprets it literally. If an opening bracket or brace is interpreted as a metacharacter, the regular expression engine interprets the first corresponding closing character as a metacharacter. If this is not the desired behavior, the closing bracket or brace should be escaped by explicitly prepending the backslash (\\) character. For an illustration, see the Example section.
1198
1198
1199
1199
1200
1200
@@ -2340,7 +2340,7 @@ Allows an <see cref="T:System.Object" /> to attempt to free resources and perfor
2340
2340
2341
2341
This method returns the first substring found at or after the `startat` character position in `input` that matches the regular expression pattern. You can retrieve subsequent matches by repeatedly calling the returned <xref:System.Text.RegularExpressions.Match> object's <xref:System.Text.RegularExpressions.Match.NextMatch%2A?displayProperty=nameWithType> method. You can also retrieve all matches in a single method call by calling the <xref:System.Text.RegularExpressions.Regex.Matches%28System.String%2CSystem.Int32%29?displayProperty=nameWithType> method.
2342
2342
2343
-
The <xref:System.Text.RegularExpressions.RegexMatchTimeoutException> exception is thrown if the execution time of the matching operation exceeds the time-out interval specified by the <xref:System.Text.RegularExpressions.Regex.%23ctor%28System.String%2CSystem.Text.RegularExpressions.RegexOptions%2CSystem.TimeSpan%29?displayProperty=nameWithType> constructor. If you do not set a time-out interval when you call the constructor, the exception is thrown if the operation exeeds any time-out value established for the application domain in which the <xref:System.Text.RegularExpressions.Regex> object is created. If no time-out is defined in the <xref:System.Text.RegularExpressions.Regex> constructor call or in the application domain's properties, or if the time-out value is <xref:System.Text.RegularExpressions.Regex.InfiniteMatchTimeout?displayProperty=nameWithType>, no exception is thrown.
2343
+
The <xref:System.Text.RegularExpressions.RegexMatchTimeoutException> exception is thrown if the execution time of the matching operation exceeds the time-out interval specified by the <xref:System.Text.RegularExpressions.Regex.%23ctor%28System.String%2CSystem.Text.RegularExpressions.RegexOptions%2CSystem.TimeSpan%29?displayProperty=nameWithType> constructor. If you do not set a time-out interval when you call the constructor, the exception is thrown if the operation exceeds any time-out value established for the application domain in which the <xref:System.Text.RegularExpressions.Regex> object is created. If no time-out is defined in the <xref:System.Text.RegularExpressions.Regex> constructor call or in the application domain's properties, or if the time-out value is <xref:System.Text.RegularExpressions.Regex.InfiniteMatchTimeout?displayProperty=nameWithType>, no exception is thrown.
2344
2344
2345
2345
]]></format>
2346
2346
</remarks>
@@ -3646,7 +3646,7 @@ Allows an <see cref="T:System.Object" /> to attempt to free resources and perfor
3646
3646
|`(?i:" + Environment.MachineName + ")`|Perform a case-insensitive match of the string that is returned by the <xref:System.Environment.MachineName%2A?displayProperty=nameWithType> property.|
3647
3647
|`(?:\.\w+)*`|Match the period (`.`) character followed by one or more word characters. This match can occur zero or more times. The matched subexpression is not captured.|
3648
3648
|`\\`|Match a backslash (`\`) character.|
3649
-
|`((?i:[" + driveNames + "]))`|Perform a case-insensitive match of the character class that consists of the individual drive lettters. This match is the first captured subexpression.|
3649
+
|`((?i:[" + driveNames + "]))`|Perform a case-insensitive match of the character class that consists of the individual drive letters. This match is the first captured subexpression.|
3650
3650
|`\$`|Match the literal dollar sign (`$`) character.|
3651
3651
3652
3652
The replacement pattern `$1` replaces the entire match with the first captured subexpression. That is, it replaces the UNC machine and drive name with the drive letter.
Copy file name to clipboardExpand all lines: xml/System.Text/UTF32Encoding.xml
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -204,7 +204,7 @@
204
204
<seelangword="true" /> to use the big endian byte order (most significant byte first), or <seelangword="false" /> to use the little endian byte order (least significant byte first).</param>
205
205
<paramname="byteOrderMark">
206
206
<seelangword="true" /> to specify that a Unicode byte order mark is provided; otherwise, <seelangword="false" />.</param>
207
-
<summary>Initializes a new instance of the <seecref="T:System.Text.UTF32Encoding" /> class. Parameters specify whether to use the big endian byte order and whether the <seecref="M:System.Text.UTF32Encoding.GetPreamble" /> method returns a Unicode Unicode byte order mark.</summary>
207
+
<summary>Initializes a new instance of the <seecref="T:System.Text.UTF32Encoding" /> class. Parameters specify whether to use the big endian byte order and whether the <seecref="M:System.Text.UTF32Encoding.GetPreamble" /> method returns a Unicode byte order mark.</summary>
Copy file name to clipboardExpand all lines: xml/System.Threading.Tasks/TaskScheduler.xml
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -79,7 +79,7 @@
79
79
80
80
<a name="Inlining"></a>
81
81
### Task inlining
82
-
In some cases when a <xref:System.Threading.Tasks.Task> is waited on, it may be executed synchronously on the thread that is performing the wait operation. This enhances performance by preventing the need for an additional thread and instead using the existing thread, which would have blocked otherwise. To prevent errors due to re-entrancy, task inlining only occurs when the wait target is found in the relevant thread's local queue.
82
+
In some cases when a <xref:System.Threading.Tasks.Task> is waited on, it may be executed synchronously on the thread that is performing the wait operation. This enhances performance by preventing the need for an additional thread and instead using the existing thread, which would have blocked otherwise. To prevent errors due to reentrancy, task inlining only occurs when the wait target is found in the relevant thread's local queue.
Copy file name to clipboardExpand all lines: xml/System.Threading.Tasks/ValueTask`1.xml
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -594,7 +594,7 @@ As such, the default choice for any asynchronous method should be to return a <x
594
594
</Parameters>
595
595
<Docs>
596
596
<paramname="left">The first value to compare.</param>
597
-
<paramname="right">The seconed value to compare.</param>
597
+
<paramname="right">The second value to compare.</param>
598
598
<summary>Determines whether two <seecref="T:System.Threading.Tasks.ValueTask`1" /> values are unequal.</summary>
599
599
<returns>
600
600
<seelangword="true" /> if the two <seecref="T:System.Threading.Tasks.ValueTask`1" /> values are not equal; otherwise, <seelangword="false" />.</returns>
@@ -663,7 +663,7 @@ As such, the default choice for any asynchronous method should be to return a <x
663
663
## Remarks
664
664
If this <xref:System.Threading.Tasks.ValueTask%601> wraps a successful result, this property returns it directly.
665
665
666
-
If it wraps a <xref:System.Threading.Tasks.Task%601>, the behavior of <xref:System.Threading.Tasks.ValueTask%601.Result%2A> is similar to the behavior of accessing <xref:System.Threading.Tasks.Task%601.Result%2A> on the wrapped task: if the task hasn't completed, accessing the property blocks the calling thread until it completes; if the task has completed successfully, the property returns the result; if the task has faulted or was cancellecd, accessing the property throws an exception. The thrown exception is not wrapped in an <xref:System.AggregateException>, which is different from the behavior of <xref:System.Threading.Tasks.Task%601.Result%2A> in the same situation.
666
+
If it wraps a <xref:System.Threading.Tasks.Task%601>, the behavior of <xref:System.Threading.Tasks.ValueTask%601.Result%2A> is similar to the behavior of accessing <xref:System.Threading.Tasks.Task%601.Result%2A> on the wrapped task: if the task hasn't completed, accessing the property blocks the calling thread until it completes; if the task has completed successfully, the property returns the result; if the task has faulted or was cancelled, accessing the property throws an exception. The thrown exception is not wrapped in an <xref:System.AggregateException>, which is different from the behavior of <xref:System.Threading.Tasks.Task%601.Result%2A> in the same situation.
Copy file name to clipboardExpand all lines: xml/System.Threading/CancellationToken.xml
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -161,7 +161,7 @@
161
161
## Remarks
162
162
If <xref:System.Threading.CancellationToken.CanBeCanceled%2A> returns `false`, it is guaranteed that the token will never transition into a canceled state, meaning that <xref:System.Threading.CancellationToken.IsCancellationRequested%2A> will never return `true`. A cancellation token that cannot be canceled is returned by the static <xref:System.Threading.CancellationToken.None%2A?displayProperty=nameWithType> property.
163
163
164
-
You can optionally use this property to determine whether a cancellation token can be canceled before examing the value of the <xref:System.Threading.CancellationToken.IsCancellationRequested%2A> property to determine whether it has been canceled.
164
+
You can optionally use this property to determine whether a cancellation token can be canceled before examining the value of the <xref:System.Threading.CancellationToken.IsCancellationRequested%2A> property to determine whether it has been canceled.
Copy file name to clipboardExpand all lines: xml/System.Threading/ManualResetEventSlim.xml
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -133,7 +133,7 @@
133
133
</Parameters>
134
134
<Docs>
135
135
<paramname="initialState">true to set the initial state signaled; false to set the initial state to nonsignaled.</param>
136
-
<summary>Initializes a new instance of the <seecref="T:System.Threading.ManualResetEventSlim" /> class with a Boolean value indicating whether to set the intial state to signaled.</summary>
136
+
<summary>Initializes a new instance of the <seecref="T:System.Threading.ManualResetEventSlim" /> class with a Boolean value indicating whether to set the initial state to signaled.</summary>
137
137
<remarks>To be added.</remarks>
138
138
<relatedtype="Article"href="~/docs/standard/threading/overview-of-synchronization-primitives.md">Overview of synchronization primitives</related>
139
139
</Docs>
@@ -170,7 +170,7 @@
170
170
<Docs>
171
171
<paramname="initialState">true to set the initial state to signaled; false to set the initial state to nonsignaled.</param>
172
172
<paramname="spinCount">The number of spin waits that will occur before falling back to a kernel-based wait operation.</param>
173
-
<summary>Initializes a new instance of the <seecref="T:System.Threading.ManualResetEventSlim" /> class with a Boolean value indicating whether to set the intial state to signaled and a specified spin count.</summary>
173
+
<summary>Initializes a new instance of the <seecref="T:System.Threading.ManualResetEventSlim" /> class with a Boolean value indicating whether to set the initial state to signaled and a specified spin count.</summary>
Copy file name to clipboardExpand all lines: xml/System.Threading/ThreadPool.xml
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -603,7 +603,7 @@
603
603
<typeparamname="TState">The type of elements of <paramrefname="state" />.</typeparam>
604
604
<paramname="callBack">An <seecref="T:System.Action`1" /> representing the method to execute.</param>
605
605
<paramname="state">An object containing data to be used by the method.</param>
606
-
<paramname="preferLocal">Unlike other QueueUserWorkItem methods, prefer exeucting in the local thread pool and not the global thread pool.</param>
606
+
<paramname="preferLocal">Unlike other QueueUserWorkItem methods, prefer executing in the local thread pool and not the global thread pool.</param>
607
607
<summary>Queues a method specified by an <seecref="T:System.Action`1" /> delegate for execution, and provides data to be used by the method. The method executes when a thread pool thread becomes available.</summary>
608
608
<returns>
609
609
<seelangword="true" /> if the method is successfully queued; <seecref="T:System.NotSupportedException" /> is thrown if the work item could not be queued.
@@ -1085,7 +1085,7 @@
1085
1085
If you specify a negative number or a number larger than the maximum number of active thread pool threads (obtained using <xref:System.Threading.ThreadPool.GetMaxThreads%2A>), <xref:System.Threading.ThreadPool.SetMinThreads%2A> returns `false` and does not change either of the minimum values.
1086
1086
1087
1087
> [!CAUTION]
1088
-
> By default, the minimum number of threads is set to the number of processors on a system. You can use the <xref:System.Threading.ThreadPool.SetMinThreads%2A> method to increase the minimum number ofthreads. However, unnecessarily increasing these values can cause performance problems. If too many tasks start at the same time, all of them might appear to be slow. In most cases, the thread pool will perform better with its own algorithm for allocating threads. Reducing the minimum to less than the number of processors can also hurt performance.
1088
+
> By default, the minimum number of threads is set to the number of processors on a system. You can use the <xref:System.Threading.ThreadPool.SetMinThreads%2A> method to increase the minimum number of threads. However, unnecessarily increasing these values can cause performance problems. If too many tasks start at the same time, all of them might appear to be slow. In most cases, the thread pool will perform better with its own algorithm for allocating threads. Reducing the minimum to less than the number of processors can also hurt performance.
0 commit comments