Allow forking from existing loggers

[SpriteOvO]

Closes #13.

To avoid confusion with the semantics of Arc::clone, I have named the new methods as fork_xxx.

Unsolved Questions

• Not sure if fn fork(self: &Arc<Self>) -> Result<Arc<Self>> (no modifier, just fork as is) is also necessary to add.

  • We chose not to implement it because we couldn't imagine a use case that needed it. (Allow forking from existing loggers #15 (comment))

[Lancern]

The meaning of "fork" should be further clarified:

Fork and configure a separate new logger.

This function creates a new logger object that inherits logger properties from self. Then this function calls the given modifier function which configures the properties on the new logger object. The created new logger object will be a separate object from self.

[SpriteOvO]

I think it would be better to replace self in your suggestion with Arc<Self>.

This function creates a new logger object that inherits logger properties from Arc<Self>. Then this function calls the given modifier function which configures the properties on the new logger object. The created new logger object will be a separate object from Arc<Self>. (No ownership sharing)

[Lancern]

LGTM.

[Lancern]

Not sure if fn fork(self: &Arc<Self>) -> Result<Arc<Self>> (no modifier, just fork as is) is also necessary to add.

I can't imagine a use case for this function. Is it necessary? What's the use case?

[SpriteOvO]

Not sure if fn fork(self: &Arc<Self>) -> Result<Arc<Self>> (no modifier, just fork as is) is also necessary to add.

I can't imagine a use case for this function. Is it necessary? What's the use case?

I can't either. So let's not implement it and wait for a feature request to be opened by someone who needs it.