Rolf Kristensen

See also: https://github.com/dotnet/runtime/issues/53432

The pretty solution would be a refactoring of NLog FileTarget, so one can override the FileAppender-factory. So NLog FileTarget gets a virtual protected method that returns a `Stream`-object from a...

Yes that is the spot.

Think it would be a great start if there was handling of ValueTypes that implements `IConvertible` without boxing (int, bool, double, decimal, datetime etc.) Guess one can do the performance...

Yes somehow the ObjectReflectionCache needs to build an object-serialization-contract (that is cached), so the object-reflection-cache can query the json-serializer what types supports "non-boxed"-serialization (only once for each type) So the...

> Essentially the entirety of ObjectReflectionCache, and all the associated classes, will have to be redone from scratch to ensure a path of preventing the boxing Also my observation. The...

> Sounds good for NLog 5! Yes already implemented with #4247 But it only reduces the overhead. It doesn't really fix the issue with negative integer values

Note that the pending #1993 includes a heavy refactoring of the FileTarget archiving logic (But doesn't include an archiving event-notifier)

An excellent case for making use of the archive events is to implement #2732 (Allowing the FileCompression to become a background task, that can also handle bulk compression of multiple...

It would make sense to have a super-cool guy/girl to setup a great notification-framework, that also allows one setup additional archive-logic. That allows a wrapper to hook into the filetarget...