Search posts, papers, and topics
3 posts · blogs.msdn.microsoft.com
Raymond Chen compares using std::call_once versus std::async (deferred) for lazy initialization in C++. He shows that std::async can be wrapped in a shared_future for repeatable get() calls, but it adds heap allocation and extra code, while call_once is tiny; exception behavior also differs.
Function‑local "magic" statics give you thread‑safe, one‑time init for static data, but they’re limited to static storage and shared across all instances. Use `std::call_once` (or a small `lazy<T>` wrapper) when you need per‑object lazy init or when the value isn’t a static. The post shows concrete code for both approaches, explains the pitfalls of using a static inside a member function, and ske…
Microsoft renumbered its job levels to start at 40‑70 to add granularity and avoid confusion with the old 1‑14 system; entry engineers now begin at level 59, while lower numbers cover interns and non‑engineering roles.
