There's some interesting and controversial stuff in here. I am very excited about extension everything. I also like the new extension method syntax; much cleaner and a much clearer expression of intent.
Lambdas vs nested functions is an example that comes to mind (during the Microsoft Build conference presentation of the feature, the presenters jokingly admitted that nested functions arose from Javascript's popularity).
I felt like the value-add of nested functions over lambdas, versus the growth of language complexity, was not great enough to add nested functions as a language feature. (Of course, that's just my opinion.)
But the bigger question is, what's the threshold where software and languages go from being "feature rich" to "bloated"? And are there cases in the past where the corporate stewards of a language have found that sweet spot?
C# has been a great language. I use it every day.
But it feels like the inevitable end game for this language, and maybe every language with corporate stewardship, is that the pressure to release new versions to "keep up with what's hot" eventually ends in the death of the technology by a thousands cuts (where, in this case, by cuts we mean unnecessary features).
(To be fair, the language stewards so far have been batting 900. They've generally done a great job at this so far.)
If you use VS for Mac its under Preferences > Text Editor > Intellisense > Show Import Items
Better yet, if it's from a NuGet package, it'll offer to install one (or several, if there are multiple candidates).
using System.Linq;
foo.Select(x => bar);
from itertools import *
imap(foo, lambda x: bar)