> For .net, I guess what you need is the symbol map (.pdb) and source code corresponding to the binary, and a tool to put it together — so that’s all achievable

> For .net, I guess what you need is the symbol map (.pdb) and source code corresponding to the binary, and a tool to put it together — so that’s all achievable now, without CallerArgumentExpression. Sounds like no one needs logs ever again! “This tool can help you make your logs better” “But did you know if you do a bunch of work you can have something better than logs?” This language feature is a small, nice feature. It provides some additional value in numerous common use cases. It may be superseded by other things that an individual may or may not have tooling support for. Never mind that for a test log with numerous failures you’d need to generate a .dmp per failure. And each .dmp needs to be individually opened, run, and analyzed. So even if you had this you still probably want as much information as is possible in the log. It’s not like this is an either-or thing. You can have both!