Thread

C++ Insights – See your source code with the eyes of a Compiler

172 points · 36 comments · rramadass

StilesCrisis · 1791036041 · focus · HN ↗
I wish the readme example showed a lambda capture. Now that's where compiler magic REALLY shows up.
1. sltkr · 1791059716 · focus · HN ↗
  C++ lambdas are just structs that overload operator(); once you realize that they become a lot less mysterious. But it's a great example of how this tool is useful to learn about those things (of course you could also read the C++ standard but who has time for that?)
  Here's an example: <a href="https://cppinsights.io/s/f04b6896" rel="nofollow">https://cppinsights.io/s/f04b6896
  (That also shows how C++'s range-based for-loops work, which is similarly some syntactic suger for a fairly mundane for-loop, but details are interesting: unlike a typical for-loop, the loop variable is declared inside the loop body.)
  1. StilesCrisis · 1791064803 · focus · HN ↗
    I said shows a lambda _capture_. This involves the compiler automatically determining which variables cross the scope boundary, and injecting code for each one.
    frabert · 1791125522 · focus · HN ↗
    I'm curious to understand which part you think is particularly interesting. The compiler clearly knows which variables are declared in what scope, so what's mysterious about figuring out which values need to be captured?

Unofficial Hacker News client; not affiliated with Y Combinator.