this post was submitted on 25 Oct 2023
16 points (90.0% liked)

Programming

17308 readers
244 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]



founded 1 year ago
MODERATORS
 

Background: I have a large serde_json value that I want to be read-only (the authoritative source is an encrypted SQLite DB and should only be updated when that gets updated)

The issue, I would like a single get function that returns a generic type

use serde_json;

pub struct Configuration {
    config: serde_json::Value,
}

impl Configuration {
    async fn get(&self, key: &str) -> Result {
        let tmp_value: = &self.config["test"];

        // This would be repeated for String, bool, etc
        if tmp_value.is_i64() {
            match tmp_value.as_i64 {
                Some(x) => Ok(x),
                Err(e) => Err(()),
            }
        } else {
            Err(())
        }
    }
}

However I get: "mismatched types expected type parameter T found type i64"

Is it even possible to return multiple types from a single function?

EDIT: SOLUTION

Here is the solution I came up with:

pub struct Configuration {}

impl Configuration {
    fn get std::str::FromStr>() -> Result {
        Ok(T::from_str("1234");
    }
}

fn main() {
    let my_conf_val = Configuration::get();
}
top 8 comments
sorted by: hot top controversial new old
[–] [email protected] 13 points 1 year ago (1 children)

No. You can only return a single type from the function. You could return the serde_json::Value though so that the code calling this function can get the value it needs itself

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago)

Afraid this might have been the case, if Ogeon's suggestion doesn't work out, I'll probably end up with multiple getters, one per type. There aren't that many anyway

Thank you!

[–] [email protected] 3 points 1 year ago* (last edited 1 year ago) (1 children)

I see two options immediately:

Make the function generic and return result(T, err), where T is the generic typed supplied by the caller (turbo fish syntax). Not sure if it will compile though.

Use whatever serve uses under the hood. They obviously have some way that allows them to return an arbitrary type. Alternatively implement it yourself by creating an enum that can be either string, int or bool. Will require matching by the caller after the function returns.

I know in e.g. java you regularly do if x.instanceof(y), but rust lends itself really badly to this type of programming.

[–] [email protected] 1 points 1 year ago

Got yourself some interesting syntax there lol. It's x instanceof Y

[–] [email protected] 3 points 1 year ago

Well how do you want to use said get function?

let x = config.get("key").await;

So what type should x have?

[–] [email protected] 2 points 1 year ago

SOLUTION:

Here is the solution I came up with:

pub struct Configuration {}

impl Configuration {
    fn get std::str::FromStr>() -> Result {
        Ok(T::from_str("1234");
    }
}

fn main() {
    let my_conf_val = Configuration::get();
}
[–] [email protected] 2 points 1 year ago* (last edited 1 year ago) (1 children)

It may be possible to use the Any trait to "launder" the value by first casting it to &Any and then downcasting it to the generic type.

let any_value = match tmp_value {
    serde_json::Value::Number(x) => x as &Any,
    // ...
};

let maybe_value = any_value.downcast_ref::< T >();

I haven't tested it, so I may have missed something.

Edit: to be clear, this will not actually let you return multiple types, but let the caller decide which type to expect. I assumed this was your goal.

[–] [email protected] 2 points 1 year ago

Correct, I would want the caller to know what they're getting, I'll see if this works, Thank you!