So, i have started creating a golfing library for Rust, as i saw some questions about it here, with some pretty good response. The usual requirement, was usually including the include statement in the byte count, and adding the library in the header of the answer. In Rust this, for me, leads to some other questions.
In Rust, with custom libraries, we usually have to do 3 things.
rustc <filename> --extern <name of crate>=<name of library file>.rlibWhich essentially is giving an extra argument to the compiler, saying that we want to use the following library, under that specific crate name.
extern crate <name of crate>;which makes it possible to access the library, from within the file in context.
use <name of crate>::<name of function, or module>::<name of function, if inside module>which puts the code needed in scope.
As you may have guessed, even with the shortest library names possible, and functions outside modules, this very quickly adds some bytes towards the answer if everything is included.
This is where my question comes into play. What actually counts as the include statement? All 3 parts of it, 2. and 3., or just 3.
Also, some answers said that one should add command line parameters towards the byte count. Does this also go for compiler arguments?
Thank you for all feedback, it would be great to have a good standard to live by. :)