4 ms·
I grepped up some old LINQ code I wrote (sanitized as it's not open source): var list = obj.FindDataNear(a, b...).Select(i => obj.GetPosition(i)) .Wher
by gary_0 2y ago
I grepped up some old LINQ code I wrote (sanitized as it's not open source):
var list = obj.FindDataNear(a, b...).Select(i => obj.GetPosition(i))
.Where(...long lambda...)
.MoreLINQ()
.ToList();
So with the style I used, the semicolon is superfluous due to indentation. Are there styles where the semicolon is useful?
- darby_nine 2y ago> So with the style I used, the semicolon is superfluous due to indentation. Eh, indentation is also conflated with block delimitation. The semicolon is still useful to more strongly indicate statement delimitation at a glance. Yes, it's redundant, but so are many signifiers around us. The pity is that readability aspects aren't semantically relevant but are stored as if they are.