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
<p>The <em>Disposable</em> interface includes the property described in <emu-xref href="#table-disposable-interface-required-properties"></emu-xref>:</p>
<p>The <dfn variants="Disposable object">Disposable</dfn> interface includes the property described in <emu-xref href="#table-disposable-interface-required-properties"></emu-xref>:</p>
<p>Invoking this method notifies the <em>Disposable</em> object that the caller does not intend to continue to use this object. This method should perform any necessary logic to perform explicit clean-up of the resource including, but not limited to, file system handles, streams, host objects, etc. When an exception is thrown from this method, it typically means that the resource could not be explicitly freed.</p>
49806
+
<p>Invoking this method notifies the Disposable object that the caller does not intend to continue to use this object. This method should perform any necessary logic to perform explicit clean-up of the resource including, but not limited to, file system handles, streams, host objects, etc. When an exception is thrown from this method, it typically means that the resource could not be explicitly freed.</p>
49807
49807
<p>If called more than once on the same object, the function should not throw an exception. However, this requirement is not enforced.</p>
49808
-
<p>When using a <em>Disposable</em> object, in most circumstances it is good practice to create the instance with a `using` declaration, as the resource will be automatically disposed when the |Block| or |Module| immediately containing the declaration has been evaluated.</p>
49808
+
<p>When using a Disposable object, in most circumstances it is good practice to create the instance with a `using` declaration, as the resource will be automatically disposed when the |Block| or |Module| immediately containing the declaration has been evaluated.</p>
49809
49809
</td>
49810
49810
</tr>
49811
49811
</table>
49812
49812
</emu-table>
49813
49813
</emu-clause>
49814
49814
49815
49815
<emu-clause id="sec-asyncdisposable-interface">
49816
-
<h1>The <em>AsyncDisposable</em> Interface</h1>
49817
-
<p>The <em>AsyncDisposable</em> interface includes the property described in <emu-xref href="#table-asyncdisposable-interface-required-properties"></emu-xref>:</p>
<p>The <dfn variants="AsyncDisposable object">AsyncDisposable</dfn> interface includes the property described in <emu-xref href="#table-asyncdisposable-interface-required-properties"></emu-xref>:</p>
<p>Invoking this method notifies the <em>AsyncDisposable</em> object that the caller does not intend to continue to use this object. This method should perform any necessary logic to perform explicit clean-up of the resource including, but not limited to, file system handles, streams, host objects, etc. When the promise returned by this method is rejected, it typically means that the resource could not be explicitly freed. An <em>AsyncDisposable</em> object is not considered "disposed" until the resulting Promise has been fulfilled.</p>
49839
+
<p>Invoking this method notifies the AsyncDisposable object that the caller does not intend to continue to use this object. This method should perform any necessary logic to perform explicit clean-up of the resource including, but not limited to, file system handles, streams, host objects, etc. When the promise returned by this method is rejected, it typically means that the resource could not be explicitly freed. An AsyncDisposable object is not considered "disposed" until the resulting Promise has been fulfilled.</p>
49840
49840
<p>If called more than once on the same object, the function should not throw an exception or return a rejected promise. However, this requirement is not enforced.</p>
49841
-
<p>When using an <em>AsyncDisposable</em> object, in most circumstances it is good practice to create the instance with a `await using` declaration, as the resource will be automatically disposed when the |Block| or |Module| immediately containing the declaration has been evaluated.</p>
49841
+
<p>When using an AsyncDisposable object, in most circumstances it is good practice to create the instance with a `await using` declaration, as the resource will be automatically disposed when the |Block| or |Module| immediately containing the declaration has been evaluated.</p>
0 commit comments