This is the correct answer. `ic(foo(123))` can be written as `print(f'{foo(123)=}')` without depending on yet another third-party library which is not pulling its weight.
I haven’t used print for debugging for ages. Now it’s all trace on azure and hope your bug ends up in the sampled data in whatever that stupid thing is called. App insights or some rubbish. Apparently a good old log file just isn’t good enough it has to be larded up with a query language. Grep was fine guys.
Looks like the project has a linked repo that appears to do a similar thing for C but it doesn't generically format the arguments.
Ah but servers and embedded, that is why telemetry, execution traces, and debugger controlled action points exist.
I haven't written my own code in months at this point...kind of depressing to think about
While the automation and systems side of my brain is thrilled that all of this id automated and integrated, developer brain is sad