The := operator should not be criticized for its similarity to the = operator in C.<br><br>In C, the = operator is error prone because occasionally the == operator is mistyped as =. If the left side is assignable, it compiles--as it is valid syntax--hiding the error until run-time. When used properly, it still provides the same elegance you mention.<br><br>The := operator would not have this issue, since the == operator should not be mistyped as :=.,(reply>), @Falk Lumo But unfortunately many non-opensource code follows this as part of the coding guidelines. Companies tend to prefer techniques that reduces the possibility of typos, unintended errors over readability anyday. Some take it to the extreme of using Hungarian notations, variable types in the variable names and so on to the point of insanity.,(reply>), @Sundar Subramaniyan <br>&gt; 0 == *p<br>That style I actually dislike because it isn't like you mentally read the condition.,(reply>), @John Madison you were an adventurer too, then you took an arrow to the knee :),(reply>), @Marino Šimić I find IDE underlining really distracting. When I was a kid I used visual studio with auto complete features. Now I read the manual (documentation) and source code, no hackishly groping my way around with autocomplete.,(reply>), @Ricardo C This isn't stack overflow. I enjoyed Marino's commentary.