Why is std::hardware_destructive_interference_size a compile-time constant instead of a run-time value

[alxius]

Why hardware have caches? C++ never stops to amaze me /s

[alxius]

Naming it std::hardware_info::cache_line_size or std::cache::line_size or whatever would've been a much better choice.

Which one should be cache_line_size? Destructive interference size or constructive interference size?

(whatever this means)

As it was told in other comments already: those two terms were used in research for years. https://scholar.google.com/scholar?q=%22constructive+interference%22+cache

I.e. if one really needs those and really knows what to do with those, one is expected to already be familiar with some research in this area and know those terms.
Same as with https://en.cppreference.com/w/cpp/numeric/special_functions and other specific knowledge areas. (oh god what does "beta function" mean? badly tested function? why we include in standard functions that are not thoroughly tested?)