Oh yeah, for sure. I just teel that I personally would never dare to release the first version of a library as 1.0.

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

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.

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”.

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.

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

imagine the diffs

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

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

Rust seems to think panicking is better: https://github.com/rust-lang/rust/issues/115482

probably the worst option for a library

Even worse than returning garbage? :)

Interestingly, Rust is what brought me to this rabbit hole. It does indeed panic in now()[1], but the devs seem to be reluctant to provide the try_now() variant[2].

[1] https://doc.rust-lang.org/nightly/src/std/sys/pal/unix/time.rs.html#124 [2] https://github.com/rust-lang/rust/issues/115482