You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The performance (may be) improved if the logger holds a reference to it's parent, instead of cloning the entire base fields, preHooks, postHooks and outputs slices/maps.
At the useReference branch, there's some suggestion:
type hooksChain struct {
parent *hooksChain
hooks Hooks
}
If this struct is used inside the logger struct, replacing the old baseFields, preHooks/postHooks and outputs field types, they will continue to have the same behavior.
The text was updated successfully, but these errors were encountered:
The performance (may be) improved if the logger holds a reference to it's parent, instead of cloning the entire base fields, preHooks, postHooks and outputs slices/maps.
At the
useReference
branch, there's some suggestion:If this struct is used inside the
logger
struct, replacing the oldbaseFields
,preHooks
/postHooks
andoutputs
field types, they will continue to have the same behavior.The text was updated successfully, but these errors were encountered: