What "advanced" features of programming languages do you use?
-
I only use var in cases where the type is either given elsewhere on the line of declaration
var frobables = new List();
var frobables2 = GetFrobables(/*params*/);or is an intermediate value whose exact type is both nasty looking and whose explicit declaration doesn't add much value.
var temp = db.tableName
.Where(x => /*filter*/)
.Select(x => new
{
x.Property1,
x.Property2,
x.Property3,
x.Property4
});I only use
dynamicin one off code, eg single shot tools or data importers; like the fluffy languages it resembles, for anything that needs to be maintained the long term costs exceed the short term savings.Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies. -- Sarah Hoyt
And you get far too many who just go "sod it, I can't be assed":
var x = 6;
foreach (var x in y.GetAll())
...There is a good blog post on it here: The Use and Abuse of the C# “var” Keyword[^]
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony AntiTwitter: @DalekDave is now a follower!
-
And you get far too many who just go "sod it, I can't be assed":
var x = 6;
foreach (var x in y.GetAll())
...There is a good blog post on it here: The Use and Abuse of the C# “var” Keyword[^]
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony AntiTwitter: @DalekDave is now a follower!
idiots can write unreadable code in any language. X|
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies. -- Sarah Hoyt
-
I use something called a "debugger". I always knew this was quite a maverick thing to do, but looking at the QA section I didn't realise just how maverick!
-
RugbyLeague wrote:
it removes a lot of unnecessary noise
Like being able to look at the declaration of a variable and know what type of object it is? ;)
Social Media - A platform that makes it easier for the crazies to find each other. Everyone is born right handed. Only the strongest overcome it. Fight for left-handed rights and hand equality.
Other than what it was invented for (linq statements and anonymous types) an example of a good use of
varis:var foo = new SomeReallyLongTemplateDeclaration>>;Here, you know what typefoois because it's type is readily apparent on the right-hand side of the statement. Basically if you can readily determine the type from the right-hand side, then it's ok to usevar. Otherwise, declare the type instead of usingvar. So here, not so good:var boo = SomeFunction();#SupportHeForShe Government can give you nothing but what it takes from somebody else. A government big enough to give you everything you want is big enough to take everything you've got, including your freedom.-Ezra Taft Benson You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
-
Try reading it as a trimmed down function (which now also allow for an arrow instead of curly braces).
// If you'd write an actual function on a single line:
myCollection.Where(bool IsActive(MyObject x) { return x.IsActive; });// Replace the {} with =>, the ; can then also be removed:
myCollection.Where(bool IsActive(MyObject x) => return x.IsActive);// The return statement isn't necessary:
myCollection.Where(bool IsActive(MyObject x) => x.IsActive);// Neither is a function name:
myCollection.Where(bool (MyObject x) => x.IsActive);// Types can usually be inferred:
myCollection.Where((x) => x.IsActive);// Remove redundant parenthesis:
myCollection.Where(x => x.IsActive);It is pretty close to the mathematical notation. Unfortunately, it doesn't always work that well.
// Example with multiple arguments, here you need parenthesis again:
myCollection.Where((x, y) => x.IsActive && y > 10);// Sometimes the type can't be inferred:
myCollection.Where((MyObject x, int y) => x.IsActive && y > 10);// You can (always) use full argument names if you like, although a single letter is common:
myCollection.Where((collectionItem, index) => collectionItem.IsActive && index > 10);Hope this explains it even further.
Best, Sander sanderrossel.com Migrating Applications to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
I've been digging into a javascript based application lately and tripped across some code that made extensive use of the arity (which is deprecated now), currying capabilities and anonymous functions. Took me a lonnnnnng time to understand what the intent and operation of the code was. So, out of curiosity, I'm wondering what "advanced" features of people's favorite languages they use on a regular basis, how they use them, and why? Or, which ones do you seldom/never use because.... E.g: ....I like using lambdas in C++ because .... (I can't think of a good example because I avoid them!) ....I avoid lambdas in C++ because they are often used where a simple function would be clearer and more readable (truth in advertising).
I use C# var extensively (basically C++ auto) in protest of lack of proper typedef support in C#
Real programmers use butterflies
-
I've been digging into a javascript based application lately and tripped across some code that made extensive use of the arity (which is deprecated now), currying capabilities and anonymous functions. Took me a lonnnnnng time to understand what the intent and operation of the code was. So, out of curiosity, I'm wondering what "advanced" features of people's favorite languages they use on a regular basis, how they use them, and why? Or, which ones do you seldom/never use because.... E.g: ....I like using lambdas in C++ because .... (I can't think of a good example because I avoid them!) ....I avoid lambdas in C++ because they are often used where a simple function would be clearer and more readable (truth in advertising).
While I use lambdas in my C# code, I don't consider them especially 'advanced'. Most of the time I'm actually averse to using such features in any language, because they tend to encourage writing clever code rather than maintainable code. Since I have code in the field older than some of you folks reading this, maintainable wins. I sporadically read news about new C++ features. None of them inspire me, as they whiff strongly of compiler weenies saying "look what I can do!". They are also overly-reliant on templates, and I find the syntax clumsy and verbose. I consider myself well-skilled in C++, and look for productivity-enhancing changes to the language. They're few and far between. C# is somewhat a different story. Most of the features I read about seem designed to improve productivity and code quality, even when they are dismissed as 'syntactic sugar'.
Software Zen:
delete this; -
I've been digging into a javascript based application lately and tripped across some code that made extensive use of the arity (which is deprecated now), currying capabilities and anonymous functions. Took me a lonnnnnng time to understand what the intent and operation of the code was. So, out of curiosity, I'm wondering what "advanced" features of people's favorite languages they use on a regular basis, how they use them, and why? Or, which ones do you seldom/never use because.... E.g: ....I like using lambdas in C++ because .... (I can't think of a good example because I avoid them!) ....I avoid lambdas in C++ because they are often used where a simple function would be clearer and more readable (truth in advertising).
I find it interesting that many seem to think 'var' is such a bad thing. In C++, there's the
autokeyword, and there's even the complementary keyworddecltypewhich is particularly useful when you want the result type of an expression, or the return type of a function. As I understand it, auto fills a similar role as var does in other language(s?), and there's actually a coding guideline promoted by Herb Sutter, no less, to 'aaa', or 'almost always [use] auto'. One of the main reasons is to help enforce type safety, which of course is outstandingly important in C++, probably more than in any other language. Another reason is maintainability: every use of auto probably doesn't need to be changed when you change some type in your code later. That said, I often deliberately don't use auto, for one (or both) of two reasons: helping with autocompletion (the editor sometimes won't know what member variables and methods to suggest when dereferencing an auto variable), readability (provided the type name is easy enough to read, rather than a nested::with), and disambiguation (when I want the value to remain unchanged - i. e.const- rather than modifiable). I suspect the former will no longer be a reason when we finally manage to switch to a newer IDE version later this year, that's why I said two reasons ;)GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)
-
While I use lambdas in my C# code, I don't consider them especially 'advanced'. Most of the time I'm actually averse to using such features in any language, because they tend to encourage writing clever code rather than maintainable code. Since I have code in the field older than some of you folks reading this, maintainable wins. I sporadically read news about new C++ features. None of them inspire me, as they whiff strongly of compiler weenies saying "look what I can do!". They are also overly-reliant on templates, and I find the syntax clumsy and verbose. I consider myself well-skilled in C++, and look for productivity-enhancing changes to the language. They're few and far between. C# is somewhat a different story. Most of the features I read about seem designed to improve productivity and code quality, even when they are dismissed as 'syntactic sugar'.
Software Zen:
delete this; -
I find it interesting that many seem to think 'var' is such a bad thing. In C++, there's the
autokeyword, and there's even the complementary keyworddecltypewhich is particularly useful when you want the result type of an expression, or the return type of a function. As I understand it, auto fills a similar role as var does in other language(s?), and there's actually a coding guideline promoted by Herb Sutter, no less, to 'aaa', or 'almost always [use] auto'. One of the main reasons is to help enforce type safety, which of course is outstandingly important in C++, probably more than in any other language. Another reason is maintainability: every use of auto probably doesn't need to be changed when you change some type in your code later. That said, I often deliberately don't use auto, for one (or both) of two reasons: helping with autocompletion (the editor sometimes won't know what member variables and methods to suggest when dereferencing an auto variable), readability (provided the type name is easy enough to read, rather than a nested::with), and disambiguation (when I want the value to remain unchanged - i. e.const- rather than modifiable). I suspect the former will no longer be a reason when we finally manage to switch to a newer IDE version later this year, that's why I said two reasons ;)GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)
I agree with Sutter about almost always using
autoand will even do this:const auto& item = ... ;
Another advantage of
autois that there are fewer affected-bys when you rename a type. Another advantage is thatautoreduces the number of line splits, which I like to avoid. -
Hover over each item each time you want to know what is? If you think that's easier and worth it, I hope you never work on my team. :-D
Social Media - A platform that makes it easier for the crazies to find each other. Everyone is born right handed. Only the strongest overcome it. Fight for left-handed rights and hand equality.
The vast majority of the time when looking at code I don't need to know what everything is - so without var I am presented with a load of noise and redundancy. If I want to know what something is and it isn't immediately obvious then I can hover over it and it tells me and for the purpose of that session I don't need to do that again. I prefer to concentrate on the code rather than a load of type declaration noise. Admittedly it is a fine line - I don't use var everywhere - int i = 10 never becomes var i = 10, for example. And using var has become something I have adjusted to over time - at first I didn't like it, then I used it to remove redundancy var l = new List() rather than List l = new List(). Now I use it in most places other than the aforementioned value type decls.
