feat: use IEnumerable Dictionary constructor

[TimothyMakkison]

Use IEnumerable Dictionary constructor

Description

Use the IEnumerable constructor if key and value mapping is synthetic.

// New
return new global::System.Collections.Generic.Enumerable.Dictionary<string, long>(source);

// Old
var target = new global::System.Collections.Generic.Dictionary<string, long>(source.Count);
foreach (var item in source)
{
    target[item.Key] = item.Value;
}
return target;

See #689

Checklist

• The existing code style is followed
• The commit message follows our guidelines
• Performed a self-review of my code
• Hard-to-understand areas of my code are commented
• The documentation is updated (as applicable)
• Unit tests are added/updated
• Integration tests are added/updated (as applicable, especially if feature/bug depends on roslyn or framework version in use)

[codecov]

Codecov Report

Merging #755 (2a3296c) into main (8f7528a) will decrease coverage by 0.01%.
The diff coverage is 88.88%.

@@            Coverage Diff             @@
##             main     #755      +/-   ##
==========================================
- Coverage   91.31%   91.30%   -0.01%     
==========================================
  Files         201      201              
  Lines        6633     6651      +18     
  Branches      821      825       +4     
==========================================
+ Hits         6057     6073      +16     
- Misses        387      388       +1     
- Partials      189      190       +1     

Files Changed	Coverage Δ
...iptors/MappingBuilders/DictionaryMappingBuilder.cs	90.55% <88.88%> (-0.28%)	⬇️

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[latonz]

Thank you for this PR 😊

[TimothyMakkison]

On second thoughts, should I close this PR and use the Dictionary<TKey, TValue>(IEnumerable<KeyValuePair<TKey, TValue>) constructor instead. This extension is just a wrapper for it, plus the constructor is available on all of .Net Core excluding .Net Standard 2.0.

I was planning on later refactoring this when I add a version detector class for #732 and to speed up checks for versioned methods

[latonz]

IMO if it is just a wrapper for the ctor we should use the ctor directly.

[github-actions]

🎉 This PR is included in version 3.3.0-next.1 🎉

The release is available on:

• GitHub release
• v3.3.0-next.1

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version 3.3.0 🎉

The release is available on:

• GitHub release
• v3.3.0

Your semantic-release bot 📦🚀