larix

joined 6 months ago
sorted by: new top controversial old
since: my first project in c/rust@programming.dev
[–] larix@programming.dev 2 points 5 months ago

 Well, that explains why it's technically possible.

As for why Option<&str> is preferrable then: It hides away your internals. Your caller should only care whether they can get the value or not (Some vs. None), not what the precise reason is. That reason or your internal structure might change.

Yes, that makes sense too. Great!

I’ve updated the code as recommended.

@Ephera@lemmy.ml @jcbritobr@mastodon.social

since: my first project in c/rust@programming.dev
[–] larix@programming.dev 8 points 5 months ago* (last edited 5 months ago) (5 children)

Thank you very much. I’ll change it. I did run cargo clippy, but it didn’t complained anything anymore before I published the code. 🙂

One question to return value Option<&String>:

is it better to change to Option<&str> or &Option<String> if the value in the struct is a Option<String>? The latter sounds more logical to me.

since: my first project in c/rust@programming.dev
66
since: my first project (codeberg.org)
submitted 5 months ago* (last edited 5 months ago) by larix@programming.dev to c/rust@programming.dev
9 comments fedilink
 

This is my first project in rust, called: since. A small tool to filter logfiles or any other files with a timestamp in it, by a given timestamp.

For example:

since 1h /var/log/messages prints all lines from the last hour. since 00:00 /var/log/messages prints all lines since 00:00.

It would be nice if you could take a look at the code. What would you change, what should I change?

I’m not a professional programmer, this is just a hobby, but I want to learn as much as possible.