From 8fcc0bf1e2f88db2bf8d3c25fdfba8a6090dd77f Mon Sep 17 00:00:00 2001 From: Dmitry-Me Date: Thu, 4 Feb 2016 17:33:59 +0300 Subject: [PATCH] No need to stick to end of method --- src/mscorlib/src/System/GC.cs | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/src/mscorlib/src/System/GC.cs b/src/mscorlib/src/System/GC.cs index 32f6407..d379117 100644 --- a/src/mscorlib/src/System/GC.cs +++ b/src/mscorlib/src/System/GC.cs @@ -270,9 +270,12 @@ namespace System { // thread. This isn't just about handles - it can happen with just // about any finalizable resource. // - // Users should insert a call to this method near the end of a - // method where they must keep an object alive for the duration of that - // method, up until this method is called. Here is an example: + // Users should insert a call to this method right after the last line + // of their code where their code still needs the object to be kept alive. + // The object which reference is passed into this method will not + // be eligible for collection until the call to this method happens. + // Once the call to this method has happened the object may immediately + // become eligible for collection. Here is an example: // // "...all you really need is one object with a Finalize method, and a // second object with a Close/Dispose/Done method. Such as the following -- 2.7.4