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
Common Razor object pooling patterns should be detectable with an analyzer. For example, for any PooledObject<T> declared within a using statement, it should be possible to detect scenarios where the object is allowed to escape beyond the using's scope. For example, in the following code, an analyzer could detect the fact list escapes its scope and report an error.
List<int>M(){usingvar_=ListPool<int>.GetPooledObject(outvar list);// use list...returnlist;}
The text was updated successfully, but these errors were encountered:
Common Razor object pooling patterns should be detectable with an analyzer. For example, for any
PooledObject<T>
declared within a using statement, it should be possible to detect scenarios where the object is allowed to escape beyond the using's scope. For example, in the following code, an analyzer could detect the factlist
escapes its scope and report an error.The text was updated successfully, but these errors were encountered: