Separate Process, Network, and Memory modules into different feature

[mokeyish]

Could you separate Process, Network, and Memory into different feature that I can enable feature flag on demand?

[GuillaumeGomez]

What advantage do you expect from this?

[mokeyish]

Thanks, I want to use Process only.

[GuillaumeGomez]

You can already if you only refresh processes. Hence my question.

[zeenix]

You can already if you only refresh processes. Hence my question.

What @mokeyish means is to allow disabling build of all the parts that are not needed by the application/library using sysinfo. Cargo.toml snippet:

sysinfo = { version = "...", default-features = false, features = ["prcoess"] }

[GuillaumeGomez]

No I understood, but my question is really about what advantages they expect from having cfged parts of the API: I expect a small improvement in compilation time but apart from that I don't really see any big advantage.

[zeenix]

No I understood, but my question is really about what advantages they expect from having cfged parts of the API: I expect a small improvement in compilation time but apart from that I don't really see any big advantage.

True but you know when you have lots of deps, small improvement from buildtime of each dep adds up fast.

[GuillaumeGomez]

True. It's something I'm interested into in the long run, but the code needs to be cleaned up a lot more before going into this, otherwise it'll be unmaintainable.

[mokeyish]

What @mokeyish means is to allow disabling build of all the parts that are not needed by the application/library using sysinfo. Cargo.toml snippet:

sysinfo = { version = "...", default-features = false, features = ["prcoess"] }

Yes, this is exactly what I mean.

[GuillaumeGomez]

Just for information, I'm currently working on separating components (#1063). After it's done, it'll be possible to think about this issue.