I don't understand why this is necessary.

You don't understand why the entire DisposeAsync implementation is necessary or why theGC.SuppressFinalize(this); is?

If you mean the whole implementation, we're calling it when the app closes to close the named pipe and remove the async receive tasks from the background.

If you mean theGC.SuppressFinalize(this) thing, it prevents the~RpcController() finalizer method from being called. Since we're not using it and we don't need to clean up any unmanaged resources here, we just tell the GC to not bother calling it during a GC run later on.

Yeah, I meantSuppressFinalize.

I don't see an explicit~RpcController() method--I assume this is implicit? Is the need to suppress it required for correctness (i.e. it is not idempotent), or is suppressing it just a performance optimization?

I ask because I'm concerned that this is somewhat fragile._speaker is the only resource that needs to be cleaned up today, but if we add a new resource and forget to include it in this method, presumably we'd leak it by supressing the implicit finalizer.

Honestly I don't know that much about how the C# GC works, so I'm not sure. From what I can tell in most cases where you don't explicitly write a finalizer it won't try to run it, so it's probably fine without it.

The main reason this is here is because thelinter said we should include it even though we don't have a finalizer:

To prevent derived types with finalizers from having to reimplementIDisposable and to call it, unsealed types without finalizers should still callGC.SuppressFinalize.

So it seems like it's more about convention