21 ms·

AWS SDK for Rust enters developer preview

• kadoban 5y ago
  Since Rust crates aren't hierarchal or namespaced, isn't have 200-300 separate AWS crates kind of asking for people to make up fake new ones and/or misspell existing?
  • ibraheemdev 5y ago
    There is work going on to allow crate namespacing (foo/bar): https://github.com/Manishearth/namespacing-rfc/blob/main/0000-packages-as-optional-namespaces.md https://github.com/Manishearth/namespacing-rfc/blob/main/000...
  • slaymaker1907 5y ago
    The design of Rust encourages having many crates because that's the only surefire way to have parallel and incremental compilation. If I were writing a large application in Rust, I would absolutely split things into as many crates as possible but keep it in a single repo for this reason.
    • ithkuil 5y ago
      The problem highlited here is not that there are distinct compilation and dependency units, bit that they are organized in a flat namespace. Anybody can create a crate like "aws-sdk-cloud" and have a crate that looks official but is not published by AWS (and is one character edit away from a legitimate AWS SDK crate)
    • beltsazar 5y ago
      Does it mean that if I change a single line of a crate, then the whole crate must be recompiled?