By mswatcher
via ericlippert.com
Submitted: Jan 17 2013 / 11:09
Previously in this series I said that the fact that the original C# compiler pursues a less aggressive strategy for optimizing away temporaries and branches from nested lifted conversions and unary operators because it suffers from “premature optimization”. That’s a loaded term and I’m not using it in the standard sense, so I want to clarify that a bit.
Tweet
SaveShareSend
Tags: .net, frameworks, other languages
-
GCJ write once, run anywhere at its finest
-
Things to Consider When Featuring Branching with Continuous Integration
-
Windows 8 UX Design Jump Start
-
C++ exceptions under the hood
-
The Kirk and Spock Approaches to Big Data
-
Good/Bad Code Study: Intention Hidden In Implementation And Misty Edge of Validity
Add your comment
