[
https://issues.apache.org/jira/browse/IGNITE-25178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-25178:
------------------------------------
Description:
It is recommended to implement *IDisposable* too when implementing
*IAsyncDisposable*:
https://learn.microsoft.com/en-us/dotnet/standard/garbage-collection/implementing-disposeasync
{code}
If you implement the IAsyncDisposable interface but not the IDisposable
interface, your app can potentially leak resources. If a class implements
IAsyncDisposable, but not IDisposable, and a consumer only calls Dispose, your
implementation would never call DisposeAsync. This would result in a resource
leak.
{code}
> .NET: Thin 3.0: ITransaction is IAsyncDisposable but not IDisposable
> --------------------------------------------------------------------
>
> Key: IGNITE-25178
> URL: https://issues.apache.org/jira/browse/IGNITE-25178
> Project: Ignite
> Issue Type: Bug
> Components: platforms, thin client
> Affects Versions: 3.0
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Priority: Critical
> Labels: ignite-3
> Fix For: 3.1
>
>
> It is recommended to implement *IDisposable* too when implementing
> *IAsyncDisposable*:
> https://learn.microsoft.com/en-us/dotnet/standard/garbage-collection/implementing-disposeasync
> {code}
> If you implement the IAsyncDisposable interface but not the IDisposable
> interface, your app can potentially leak resources. If a class implements
> IAsyncDisposable, but not IDisposable, and a consumer only calls Dispose,
> your implementation would never call DisposeAsync. This would result in a
> resource leak.
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
