J
jwgoerlich
Hello group,
I have been reviewing Microsoft's webinars and documents on C# JIT
optimizations. One, Designing .Net Class Libraries, said that this
code:
for (i = 0; i < a.Length; i++) { ... }
Is faster than this:
int l = a.Length;
for (i = 0; i < l; i++) { ... }
For arrays. This was because of how the CLR handles bounds checking. Is
the same true for strings and StringBuilders?
J Wolfgang Goerlich
I have been reviewing Microsoft's webinars and documents on C# JIT
optimizations. One, Designing .Net Class Libraries, said that this
code:
for (i = 0; i < a.Length; i++) { ... }
Is faster than this:
int l = a.Length;
for (i = 0; i < l; i++) { ... }
For arrays. This was because of how the CLR handles bounds checking. Is
the same true for strings and StringBuilders?
J Wolfgang Goerlich