Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@Pyjong I guess I've figured it out. Files and modules have basically nothing to do with eachother except for special files: main.rs, lib.rs and mod.rs. Naked "mod" is needed to declare that other source files even exist. "Use" is used to... well import modules from the virtual module tree, which is filled via "mod"-blocks from any source file
-
@Pyjong Actually, scrap everything I've just said
When you realize that you're googling an error message you've implemented yourself
That's exactly how I started, am I a Machine!? ... learning Machine Learning
Holy shit I don't understand Rust's module system. Package I have not a single clue what it is... It "can contain one library crate and multiple binary crates". What? Okay so a crate is a collection of modules. Great, now how do you define modules? `mod whatever {}` probably. Then what the hell does `mod whatever;` do?? Import a module from a file with the same name (ignoring the fact that modules and files don't seem to have anything to do with each other). But why `mod` to import? How does that differ from `use`-ing a module? What is any of this??
rant
confused
rust