Fix Threads import for package precompilation

Author: abcdvvvv

docs/src/functions.md

@@ -4,11 +4,11 @@ CurrentModule = ComponentLogging
 
 # Function API
 
-This page documents the **function-first** logging APIs exported by `ComponentLogging`.
-All functions require the logger to be passed explicitly as the first argument.
-In application code you will typically define *forwarding helpers* to avoid threading the logger manually.
+This page documents the function-based logging interface exported by `ComponentLogging`.
 
-When you already have a logger available (e.g. stored in a `const` or a `Ref`), calling `clog(logger, ...)` bypasses the task-local logger lookup performed by stdlib logging macros (`@info`, `@logmsg`, …) and can reduce overhead in hot paths.
+These functions take a logger explicitly as their first argument. In application code, `@forward_logger` can generate forwarding methods when repeatedly passing the same logger would be inconvenient.
+
+When a logger is already available, for example in a `const` or `Ref`, calling `clog(logger, ...)` avoids the module-registry lookup used by the logging macros and can reduce overhead in frequently executed code.
 
 ## Forwarding macro
 

docs/src/macros.md

@@ -4,10 +4,9 @@ CurrentModule = ComponentLogging
 
 # Macros API
 
-This page documents the **macro-first** logging APIs exported by `ComponentLogging`.
+This page documents the logging macros exported by `ComponentLogging`.
 
-Macros work differently from functions. Macros do not take a logger as an argument; instead, you need to bind a key-value pair of `current module => logger` to the internal module registry of ComponentLogging.
-Subsequent macro calls do not require passing the logger; the logger for the current module is retrieved via a dictionary lookup.
+Unlike the function API, the macros do not take a logger explicitly. Instead, a logger is associated with a module in the internal module registry. Each macro call retrieves the logger bound to the calling module, falling back through its parent modules when necessary.
 
 You can use `set_module_logger` or `@bind_logger` in the `__init__` function to bind the logger to the current module.
 

src/ComponentLogging.jl

@@ -1,6 +1,6 @@
 module ComponentLogging
 using Logging
-using Threads: Atomic
+using Base.Threads: Atomic
 
 include("PlainLogger.jl")
 export PlainLogger