HackerTube 中文?

CppCon 2019: Chandler Carruth “There Are No Zero-cost Abstractions”

CppConYouTube ↗

Further reading 1

What does a module promise its callers? →Try replacing a module whose callers rely on its incidental return order. Start with what the interface says, then trace the decisions it hides and the behaviors people have learned to expect.This video helps answer · Where did the hidden cost go?

Caption notes

Carruth separates runtime, build-time and ABI costs. Removing instructions from a hot path can move work into compilation, while ownership wrappers may still encounter calling-convention constraints.

Video or transcript source ↗
Original passages · 2
it just means the cost is paid somewhere else
CppCon 2019: Chandler Carruth “There Are No Zero-cost Abstractions” · ▶ 16:44–16:51
that's a change to the calling convention of C++
CppCon 2019: Chandler Carruth “There Are No Zero-cost Abstractions” · ▶ 27:07–27:16

Hacker News comments

View original on HN ↗