Repository navigation
Port System.Collections docs for .NET 9 APIs #105976
Description
Activity
- addeddocumentationDocumentation bug or enhancement, does not impact product or test codeDocumentation bug or enhancement, does not impact product or test code
on Aug 5, 2024 dotnet-policy-service commented
on Aug 5, 2024 ContributorMore actionsTagging subscribers to this area: @dotnet/area-system-collections
See info in area-owners.md if you want to be subscribed.Here's a PR that ports some that we missed in the first pass: dotnet/dotnet-api-docs#10209
P7 Undoc APIs as of 08/20:
With the exception of all the
TryGetValuemethods, everything else in this table appears to be documented in source, for example the entry in the first row:Lines 247 to 258 in d756692
/// <summary> /// Gets an instance of a type that may be used to perform operations on a <see cref="ConcurrentDictionary{TKey, TValue}"/> /// using a <typeparamref name="TAlternateKey"/> as a key instead of a <typeparamref name="TKey"/>. /// </summary> /// <typeparam name="TAlternateKey">The alternate type of a key for performing lookups.</typeparam> /// <param name="lookup">The created lookup instance when the method returns true, or a default instance that should not be used if the method returns false.</param> /// <returns>true if a lookup could be created; otherwise, false.</returns> /// <remarks> /// This instance must be using a comparer that implements <see cref="IAlternateEqualityComparer{TAlternateKey, TKey}"/> with /// <typeparamref name="TAlternateKey"/> and <typeparamref name="TKey"/>. If it doesn't, the method will return false. /// </remarks> public bool TryGetAlternateLookup<TAlternateKey>(out AlternateLookup<TAlternateKey> lookup) where TAlternateKey : notnull, allows ref struct Running the tool again locally seems to be skipping over these missing docs as well. @carlossanlop any suggestions or should I just port the missing docs manually?
- addedin-prThere is an active PR which will close this issue when it is mergedThere is an active PR which will close this issue when it is merged
on Aug 29, 2024 Running the tool again locally seems to be skipping over these missing docs as well. @carlossanlop any suggestions or should I just port the missing docs manually?
That's not good. What command were you using? Do any of the APIs live under System.Private.CoreLib?
I followed the instructions from the parent issue. Some APIs are SPCL but others are regular libs so I don't think it's related.
Reopening as there were new APIs introduced in RC1. @eiriktsarpalis
Adding @buyaa-n for some load-balancing.
The missing APIs are documented in source. I re-ran the porting tool and hit the same issue I reported in #105976 (comment). At the time I had hand-ported the missing docs to
dotnet-api-docsin dotnet/dotnet-api-docs#10338 but the APIs got moved to a different location in RC1. Unless somebody else picks this up, I'll look at re-hand porting the docs later in the week or next week but ideally this should be solved in the tooling.- locked and limited conversation to collaborators
on Nov 9, 2024
Below is the list of APIs that still show up as undocumented in dotnet-api-docs and were introduced in .NET 9.
Full porting instructions can be found in the main issue.
This task needs to be finished the day before the RC2 snap (September 15th).
RC1 APIs as of 2024/10/01: #105976 (comment)