I started implementing ILogger<T> but hit a runtime constraint: interface dispatch (ILogger.Log()) is not available during LibraryInitializer.InitializeLibrary() because CachedInterfaceDispatch / DispatchResolve aren't fully initialized yet. Using ILogger<T> in any code called during init causes an infinite exception loop at boot.

The problem is that Core and HAL code runs both during init (before the runtime is ready) AND after init (when the runtime is fully initialized). So we can't just use ILogger<T> in those files since they'd crash when called during boot.

Options:

Static Log class only (like Linux printk). Static methods with log levels, [Conditional("COSMOSDEBUG")] on Debug/Trace to compile them out in release. Works everywhere, no interfaces. Simple but not the standard .NET pattern.
Static Log internally + ILogger<T> for user kernels or Cosmos.Kernel.System. Kernel internals use the static Log class. ILogger<T> is exposed for user kernel code or Cosmos.Kernel.System where the runtime is initialized.
Use ILogger<T> everywhere but guard init-time calls. Needs a mechanism to detect whether the runtime is initialized and fall back to direct Serial writes during init.

@zarlo @Guillermo-Santos any thoughts?

Implement a good layered log system #233

Description

Activity

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions