set-logger! macro evaluates args to early

[cch1]

If I programmatically call set-logger! with a run-time determined argument, it's not possible to configure the root logger since the (keyword? logger) function has already been evaluated.

The (keyword? logger) function needs to be evaluated at runtime, not macro expansion time.

[darwin]

Confirmed. This is clearly a limitation which can be easily fixed.

Workaround: use set-loggers! directly.