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
It can likely be replaced with a dictionary, or directives can become symbols and use the same lookup mechanisms are other symbol types use.
// From guideline prose:// "When implementing such a custom collection, follow the API pattern// established by Collection<T> and ReadOnlyCollection<T> as// closely as possible. That is, implement the same members explicitly,// name the parameters in the same way that these two collections name// them, and so on. In other words, make your custom collection different// from these two collections only when you have a very good reason to// do so."publicclassDirectiveCollection:IEnumerable<KeyValuePair<string,IEnumerable<string>>>,IEnumerable{publicDirectiveCollection();publicboolContains(stringname);publicIEnumerator<KeyValuePair<string,IEnumerable<string>>>GetEnumerator();publicboolTryGetValues(stringname,refIReadOnlyList<string>values);}
changed the title [-]Consider removing this type. It can likely be replaced with a dictionary, or directives can become symbols.[/-][+]Consider removing `DirectiveCollection`[/+]on Nov 2, 2022
Activity
[-]Consider removing this type. It can likely be replaced with a dictionary, or directives can become symbols.[/-][+]Consider removing `DirectiveCollection`[/+]remove DirectiveCollection, use dictionary instead, fixes dotnet#1912
Remove CompletionDelegate, CompletionSourceList and DirectiveCollecti…