slog-atomic 0.3.0 out of date with master about slog HOT 5 CLOSED

Yes. I also advise to stick with published version, and use http://docs.rs to get current docs.

from slog.

Should be fixed now. Comments always welcome. :)

from slog.

Thanks!

Generally I find it quite confusing with the plethora of independent crates that are not kept in sync with published documentation and examples. From a maintenance point of view, a single extern crate slog dependency would be easier to manage as figuring out what different crate versions are compatible has been a challenge.

from slog.

I understand. Now that core slog crate is stable, every other crate should depend on slog = "1", so cargo should have easier time just picking a version for you. Right now it was just me, that did not publish atomic after the final breaking change: 1.0.0.

The reason why they are broken up in pieces is that each crate pull in more dependencies, so having them in one crate would pull a lot of dependencies. Then they are broken up, you're paying just for what you're using. Especially for libraries, that don't actually prepare any drain, that's a huge benefit, as they depend only on tiny slog core crate.

If it keeps being an inconvenience please get back to me. :) . Maybe eg. we could create slog-all crate the rexports both slog and all other (sometimes interdependent) slog crates in a one set or something. We'll see how it plays out.

from slog.

Thanks for your elaborate reply!

I have some theoretical appreciation for why the library is built the way it is, but I’m not convinced the need to depend on e.g. slog-atomic or slog-term independently from slog, or the minor improvements in build time, makes up for this complexity.

An alternative scheme would be to synchronise and force-push each crate’s version number when changes occur, so that when a change happens in slog-atomic, all crates are pushed to the same version, making a consumer’s Cargo.toml file easier to maintain:

slog = "^1"
sloc-atomic = "^1"
…

Under any circumstances, I expect changes to be more minor now that the library has reached a stable version number, and I don’t expect the changes in the coming versions to be as bad to adapt to. So please take these comments with a grain of salt (-:

from slog.