Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)H

hades

@ hades @programming.dev

Posts
1
Comments
16
Joined
1 yr. ago

  • idemkit: runs your code once per key, even when two requests race or a worker dies

    Jump

  • If you follow semantic versioning rules (https://semver.org/) there is actual semantic difference between major version 0 and major version 1 and above.

  • idemkit: runs your code once per key, even when two requests race or a worker dies

    Jump

  • A bit ballsy to release the 1.0.0 version immediately, isn’t it? :)

    Other than that, kudos for sharing with the world, surely it will come useful for someone. Hell, I might even use it for things like host maintenance cronjobs instead of lock files.

  • Feedback for first Rust Program

    Jump

  • Yep, exactly. You can actually look at their source code, it should be very good for learning.

  • Feedback for first Rust Program

    Jump

  • Rust Error Handling and Rust in General is still a big black box for me yet to be unveiled :D

    Conceptually, error handling in Rust is incredibly simple: if a function can fail, its return type is an enum of either the result of the function (in case of success) or a description of the error that happened. This enum is called Result. See:

    why do i need crates for error handling?

    You don't. You can 100% handle errors without any additional dependencies, and probably you should be doing that in the beginning. The crates simply add a little bit of syntactic sugar to simplify some boilerplate that you'll have to start writing as soon as your error handling gets sufficiently complex.

  • Feedback for first Rust Program

    Jump

  • Welcome to Rust, I hope you enjoyed learning and using it :)

    One major advice would be to run cargo clippy, which gives a lot of helpful hints. Apart from that I also have some feedback.

     
        
    40	struct VendorOuiData {
    41	    vendor_organization: String, // Vendor Organization

    These comments should be doc-comments (///) so that cargo doc picks them up.

     
        
    49	fn fetch_oui_database(url_string: &String) -> Result<String, Box<dyn std::error::Error>> {

    Not saying that your return type is bad, but in general you might be interested in crates thiserror and anyhow that simplify error handling.

     
        
    51	        .timeout(Duration::new(60, 0))

    Duration::from_mins(1) would be much more readable.

     
        
    66	                panic!("{}", err);

    You should almost never panic. Your function already returns a Result<>, so you should be using that for error handling.

     
        
    70	    } else {
    71	        // HTTP Status is not 200

    Not Rust specific, but usually I recommend to handle errors first, and return from the function early. This way you reduce cognitive load on the reader, and reduce nesting of if-blocks.

     
        
   150	                let mut parts = line.splitn(2, '\t');

    There's a convenient method to split in two substrings that you could have used:

     
        
let (mac_address, vendor_organization) = line.split_once('\t').unwrap_or(("", ""));

  

     
        
   166	                vendor_oui_data.vendor_address += line
   167	                    .trim()
   168	                    .split(' ')
   169	                    .filter(|s| !s.is_empty())
   170	                    .collect::<Vec<_>>()
   171	                    .join(" ")
   172	                    .as_str();

    I would probably write a regular expression that replaces all contiguous whitespace with a single space instead.

     
        
   173	                vendor_oui_data.vendor_address.push('\n');

    Aren't you trimming this new line off in line 181?

     
        
   181	        vendor_oui_data.vendor_address = vendor_oui_data.vendor_address.trim().to_string();

    This is somewhat inefficient, since you'll be allocating and copying your string here.

  • Can I get a computer science degree, certs,or education without ever touching Windows?

    Jump

  • Computer science is just mathematics, you can do it with pen and paper. The actual IT jobs where you don't have to touch windows are plentiful, although it might be a bit of a red flag if you're vehemently refusing to touch some specific software (be it windows, or any other program, or programming language).

  • Reversing a string in Rust (for no reason)

    Jump

  • That chars() call hides a lot of complexity, but also even that might not be correct depending on what exactly you mean by “reversing a string”.

  • Reversing a string in Rust (for no reason)

    Jump

  • Thank you for watching the video and answering the question that I had from just reading the title.

    Reversing a UTF-8 string is super hard in any language, rust doesn’t really make it that much harder.

  • Serverless Is An Architectural Handicap (And I'm Tired of Pretending it Isn't)

    Jump

  • Just an ad article. "Did you also encounter skill issues while building web applications? Try my platform."

  • Every goto in the Linux kernel / Just another day on the linux-kernel mailing list

    Jump

  • but how many COMEFROMs are there

  • Recto: In Case Programming Isn’t Hard Enough

    Jump

  • imagine the diffs

  • Handling of unlikely syscall errors

    Jump

  • Uninitialized automatic variables. E.g. (in C/C++):

     cpp
        
int get_time() {
  int time;
  syscall(/* something that fails */, &time);
  return time;
}

  • Handling of unlikely syscall errors

    Jump

  • Handling of unlikely syscall errors

    Jump

  • probably the worst option for a library

    Even worse than returning garbage? :)

  • Handling of unlikely syscall errors

    Jump
  • Programming @programming.dev
    hades @programming.dev

    Handling of unlikely syscall errors