Nicholas Blumhardt

One note regarding the alignment issue; fixing it will create a regression for anyone currently relying on it to squeeze two properties into the space of one, e.g. `{RequestId,10}{MessageId,10}` in...

Thanks, Thomas; unfortunately the interpolated string handler API doesn't account for parameter names, which substantially reduces the quality of logged events. There are a few past discussion threads in this...

@ThomasMader thanks for your reply. It would have to be the C# compiler that added support for property names. The code generated by the compiler calls `AppendLiteral()` with literal text,...

That's interesting, @kulakovt - I hadn't considered `CallerArgumentExpression`, here. Worth some more thought. I'm still unsure about how easy it would be to create low-quality structured log events this way,...

Thanks for all the follow-ups! @kulakovt - > > Will analyzing property names lead to perf problems? > > This is entirely the work of the compiler. After compilation, all...

Thanks for dropping by, @fedarovich! The main problem with `LogInformation("{1 + 1:SomeName}")` is that it's already quite common to use formatting with log messages, e.g. `LogInformation("{1 + 1:x8}")`. It'd be...

(Fixed a typo in the last comment after posting, in case you read the initial version via email...)

Thanks for the reply! > Because in the current version of Serilog this is valid code (this will work): It's not valid Serilog usage, though:  But the interpolated version...

Thank you for your suggestion, Dani. One way this might be emulated, currently, is to enable `SelfLog` and re-emit an event through the Serilog pipeline if the text matches the...

Appealing idea 👍 - I wonder if using `ReadFrom.AppSettings(strict: true)` might be more bullet-proof than using the settings themselves (i.e. the user might mistype the `mode` directive and then wonder...