miniblog.

← Back to all posts
Mar 6, 2017 at 19:36
Crystal clear intro to the challenges of inlining with good debug info https://docs.google.com/presentation/d/1Wcblp3jpfeKwA0Y4FOmj63PW52M_qmNqlQkNaLj0P5o/edit#slide=id.p (even though Go lets you inspect the stack!)
talk: Mid-stack inlining in the Go compiler (external)
talk: Mid-stack inlining in the Go compiler (external)
Mid-stack inlining in the Go compiler David Lazar mentored by Austin Clements

Related Posts

Jul 29, 2023 at 17:33
Go has a wonderful, accessible discussion of how it does inlining today, the downsides, and the plans for 1.22:
Go 1.22 inlining overhaul
Go 1.22 inlining overhaul
Go 1.22 inlining overhaul , with contributions from , , , and Last update: The Go compiler’s inliner has never been particularly good. It wasn’t until Go 1.12, released in 2019, that the Go compiler supported inlining more than leaf functions, and we’ve slowly chipped away at more limita...
Aug 3, 2021 at 03:40
On the nuances of Rust inlining, crate boundaries, and what gets inlined by default: https://matklad.github.io/2021/07/09/inline-in-rust.html
Dec 28, 2020 at 06:34
1
It's well known that certain compiler optimisations matter way more than others (e.g. inlining). Is there a similar principle for linters? I find red squiggles under unused/undefined variables the single most useful check.