env_logger::init_or_default("mylib=warn")

[stepancheg]

Function parameter is used as logging spec when RUST_LOG variable
is not available.

[dtolnay]

Thanks! How would you feel about accomplishing this with LogBuilder instead?

let mut lb = env_logger::LogBuilder::new();
lb.parse(&env::var("RUST_LOG").unwrap_or("mylib=warn".to_owned()));
lb.init()?;

I am concerned that init_or_default does not compose well with other functionality we may want to expose here, for example try_init from #146.

[dtolnay]

Thanks! How would you feel about accomplishing this with LogBuilder instead?

let mut lb = env_logger::LogBuilder::new();
lb.parse(&env::var("RUST_LOG").unwrap_or("mylib=warn".to_owned()));
lb.init()?;

I am concerned that init_or_default does not compose well with other functionality we may want to expose here, for example try_init from #146.

[stepancheg]

It is inconvenient to repeat this fragment in each unit test, in each bench, in each of several main functions. Or create a library with just this function.

init_or_default does not solve any otherwize unsolvable problems, it's just convenient to have.

[dtolnay]

Seems reasonable. Could you come up with some approaches for making this compose better with other functionality, especially #146?

Here is one idea to get you started:

LogBuilder::new().parse("mylib=warn").parse_env().init();

[KodrAus]

Thanks @stepancheg! Do you mind rebasing this over at https://github.com/sebasmagri/env_logger, which is the new home for env_logger?

It would be good for this to be composable within the builder.

[KodrAus]

I'll go ahead and close this now, please feel free to file against the new env_logger repo.