Merge future branch back into master

[weshaggard]

This issue is just for tracking the changes we have merged into future so when we merge it back to master we know which API changes we need to modify contracts and ensure are supported on our other platforms like the desktop framework. At this point it isn't clear when this will happen but we want to keep track of this item.

--- Merged PRs into future ---

• [Api-addition] Regex group should provide a Name property. corefx#1384 Regex group should provide a Name property.
• Add ConcurrentDictionary GetOrAdd/AddOrUpdate overloads with generic arg corefx#1783 Add ConcurrentDictionary GetOrAdd/AddOrUpdate overloads with generic arg
• Implement generic interfaces on Regex collections corefx#1756 Implement generic interfaces on Regex collections
• Add async XLinq document/element loading and saving corefx#2436 Add async XLinq document/element loading and saving
• Add HashSet<T> ctors with capacity corefx#2862 Add HashSet ctors with capacity

[karelz]

@weshaggard is it still needed?

[stephentoub]

I don't believe most of the above mentioned PRs/commits were ever brought back to master, but they were valid additions for approved new APIs.

[weshaggard]

Agreed. We should get these merged into master and added directly to .NET Core similar to what @ericstj is doing in dotnet/corefx#11272.

[Priya91]

dotnet/corefx#1384 Regex group should provide a Name property.

This is in master, and also in full framework.

[karelz]

Updating the list to list of check boxes - marking dotnet/corefx#1384 as done per Priya's comment.

[justinvp]

Is this planned for the 1.2 timeframe? If so, should it be moved to the 1.2 milestone? If not, and I want to expose some of the new APIs for 1.2, should I just manually port those individual commits from Future to Master?

[karelz]

It will happen in 1.2, only if we have time. If you or anyone else wants to help, that would be great.

@weshaggard can you please confirm there is nothing preventing us to take ports of the changes into master? (i.e. if @justinvp or someone create the port, we can take it)

[weshaggard]

There shouldn't be anything blocking these APIs now. I suspect it will not be as simple as merging the changes to master. We will need to expose them as .NET Core app specific APIs.

[justinvp]

The following two can be checked off:

• Implement generic interfaces on Regex collections corefx#1756 Implement generic interfaces on Regex collections (fixed by Implement generic interfaces on Regex collections for netcoreapp1.1 corefx#12596)
• Add HashSet<T> ctors with capacity corefx#2862 Add HashSet ctors with capacity (fixed by Expose HashSet<T> ctors with capacity in netcoreapp1.1 corefx#12600)

[karelz]

Marked as such, thanks @justinvp!

[justinvp]

Now that dotnet/corefx#13828 has been merged, the ConcurrentDictionary change can be checked-off. The only remaining work item is:

• Add async XLinq document/element loading and saving corefx#2436 Add async XLinq document/element loading and saving

[karelz]

Awesome, thank you very much @justinvp for your help!