3 ms·

No, the last commit was two days ago: https://github.com/ruma/ruma-events/commit/c7d7212b000e324b96cc66c252e77c6297fdfda7 https://github.com/ruma/ruma-events/co

by jeltz 7y ago

No, the last commit was two days ago: https://github.com/ruma/ruma-events/commit/c7d7212b000e324b96cc66c252e77c6297fdfda7 https://github.com/ruma/ruma-events/commit/c7d7212b000e324b9... It is a bit hard to follow their project since they have split it up in so many tiny repos. I personally prefer when a set of closely related crates are developed in one mono repo.

Coding_Cat 7y ago
For rust it's sometimes useful to split it like that, because it makes it easy to publish small subsets of your project on cargo. Say you develop a custom datastructure, or an extension on Streams. The same applies to other languages to some degree, but crates/cargo just makes it very painless to grab crates that are on a seperate git.
- jeltz 7y ago
  But Cargo supports having multiple crates in the same git repo. Many projects do this like regex (regex and regex-syntax are in the same repo) and openssl (openssl, openssl-sys, openssl-errors). Maybe I am missing something but it seems very easy to handle multiple closely related crates in the same repo.
  - kibwen 7y ago
    What makes this possible is Cargo's "workspace" feature, which is relatively new enough that it's not hard to imagine that some older projects may simply predate it.
    - mcny 7y ago
      Would something like git subtree help here? Allow people to continue working with their individual repos but present a unified view for outsiders to follow along? We could automate this, right?
    - jeltz 7y ago
      Hm, I have been doing this just fine without using the workspaces. What am I missing?
      - exrook 7y ago
        Cargo workspaces are more of an optimization in that they let all the crates in your project share the same output directory[0], so built dependencies can be shared among every crate, as opposed to each crate needing to (re)build all of its dependencies independently. This helps to reduce compile times when working on projects where you frequently switch between crates. [0] https://doc.rust-lang.org/book/ch14-03-cargo-workspaces.html https://doc.rust-lang.org/book/ch14-03-cargo-workspaces.html
est31 7y ago
Oh indeed, thanks for pointing out! Wishing them luck then.

by jeltz 7y ago

Coding_Cat 7y ago

For rust it's sometimes useful to split it like that, because it makes it easy to publish small subsets of your project on cargo. Say you develop a custom datastructure, or an extension on Streams. The same applies to other languages to some degree, but crates/cargo just makes it very painless to grab crates that are on a seperate git.

jeltz 7y ago
But Cargo supports having multiple crates in the same git repo. Many projects do this like regex (regex and regex-syntax are in the same repo) and openssl (openssl, openssl-sys, openssl-errors). Maybe I am missing something but it seems very easy to handle multiple closely related crates in the same repo.
- kibwen 7y ago
  What makes this possible is Cargo's "workspace" feature, which is relatively new enough that it's not hard to imagine that some older projects may simply predate it.
  - mcny 7y ago
    Would something like git subtree help here? Allow people to continue working with their individual repos but present a unified view for outsiders to follow along? We could automate this, right?
  - jeltz 7y ago
    Hm, I have been doing this just fine without using the workspaces. What am I missing?
    - exrook 7y ago
      Cargo workspaces are more of an optimization in that they let all the crates in your project share the same output directory[0], so built dependencies can be shared among every crate, as opposed to each crate needing to (re)build all of its dependencies independently. This helps to reduce compile times when working on projects where you frequently switch between crates. [0] https://doc.rust-lang.org/book/ch14-03-cargo-workspaces.html https://doc.rust-lang.org/book/ch14-03-cargo-workspaces.html

est31 7y ago

Oh indeed, thanks for pointing out! Wishing them luck then.