Understanding and optimizing compiler time (just a bit)

[Tamas_Papp]

I think that happened because the original code was somewhat naively written. I am now facing the following dilemma: I want stack allocation (so, SArray) but no excessive specialization based on size (so, no SArray). Instead of continuing this discussion with a tangent, I opened a new one here:

Stack-allocated arrays without excessive compilation time

I find SArray very useful because they are stack-allocated — this is important generally, but specifically for threaded code I find that minimizing allocations is a must. However, I also fine that excessive use of SArray, especially for nested types (which can be also SArrays, or ForwardDiff.Dual, etc) really taxes the compiler. I am looking for a general strategy of implementing a vector (or array, that follows easily) which can be stack-allocated, but does not generate specialized code bas…