HaloFour

> On the other hand, I can't find a way to actually produce a truncated stack trace besides vendoring in the logic from `Throwable#printStackTrace()`, so not how useful it would...

These rules sound very similar to the coherence rules enforced by Rust. My opinion is that such limitations are fatally limited in that I expect that the _vast, vast, vast_...

My other issue with a design like this is that by impacting the type at runtime you lose all of the scoping mechanisms that exist for extensions in general. IMO,...

Should the refactoring encourage interpolation in that case or the simpler (and more efficient) concatenation? Or provide the option to do either?

> Attribute parameters This proposal includes changing the runtime to understand and support for more types in attribute parameters? Would that also include the pseudoconstant `decimal`?

It was noted that there is a NuGet package which uses an extension method and some overloaded operator chicanery to mimic this language feature: https://github.com/dotnet/roslyn/issues/136#issuecomment-71959890 However, if the compiler will...

I think I could live with the exception info being written directly as attributes to the span. I do have some concerns about the API becoming very opinionated as to...

Importantly, does that mean that projects that aren't using OTel logging are simply not going to be able to observe exceptions?