crossbeam-epoch | Epoch-based garbage collection | Machine Learning library

• crossbeam_epoch::Shared is a smart pointer. That is, a pointer plus extra stuff. In C++ or Rust, smart pointer is the term used for a pointer wrapper which adds any of the following:

  • Ownership information
  • Lifetime information
  • Packing extra data in unused bits
  • Copy-on-write behavior
  • Reference counting

  In that context, a raw pointer is just the wrapped pointer, without all the extra stuff.

• crossbeam_epoch::Shared fits (among others) in the “Packing extra data in unused bits” category above. Most data in modern computers is aligned, that is, addresses are a multiple of some power of two. This means that all low bits of the addresses are always 0. One can use that fact to store a few extra bits of information in a pointer.

  This extra data is called tag by this particular library, however that term isn't as common as raw pointer.

It looks like I missed installing some dependencies.

sudo apt install pkg-config libasound2-dev libssl-dev cmake libfreetype6-dev libexpat1-dev libxcb-composite0-dev

https://github.com/amethyst/amethyst#debianubuntu

First things first, go back and re-read The Rust Programming Language's chapter on "Packages, Crates, and Modules". This discusses several fundamental concepts that are vital for understanding.

Why can I not clone a git project, add a main.rs and import one of the structs?

To me, this feels like the same question as "why can't I reach into another human, grab their lungs, and then use them to breathe"? You simply cannot download some arbitrary Rust library and start pulling random files out of it and expect them to work.

Specifically in your case, all libraries have a lib.rs that is the crate root. The crate root tends to have many common definitions that are needed by the rest of the code and imports all the submodules. When you create a main.rs and declare the modules from the library as your own, your main.rs becomes the crate root, but it doesn't define all the things that the library needs. This causes the code to fail to compile.

Instead, just use the crate as a library, as it's intended.

The easiest thing to do create a new Cargo project and add the crate as a dependency to your Cargo.toml. The gitlab crate is already distributed on crates.io, so you just add the version number:

So turns out the issue was with the COPY . . command, as it just copied everything into /, which was then attempted to be compiled (At least that's my belief).