It’s funny how it used to be expensive. In Danish we have a saying to say someone is poor if “they can’t even afford salt for their egg”, as if an egg is cheaper than salt. Because it actually used to be that way.

One more vote for using WASM. Using WASM has the benefit of allowing the user to use almost whatever language they want, as long as it can compile to WASM. So the user doesn’t have to learn some bespoke scripting-specific language.

Definitely let go. Rust has some OOP features, but it’s mostly just the OOP idea of interfaces, which Rust models with traits. You can also do dynamic dispatch, which is another OOP feature, but you should almost never use this in Rust unless you absolutely have to. Then there’s encapsulation which is hugely important in Rust too, but yea outside of that kind of thing, I don’t think OOP patterns are too useful. Honestly, if you ask me, many of these “OOP patterns” are really just solving problems that OOP causes in the first place.

Feel free to ask any other questions.

Thanks for explaining further, it’s a lot clearer now what you want to do. And no, I don’t think this DAO thing is idiomatic for Rust and you probably don’t want to do it like that. I’m not familiar with the pattern though, I’m not too much into OOP myself.

Anyways, I’ve worked a lot with axum and sqlx before so I can tell you what I’d do.

I am writing an axum backend which (like other backends) needs to do stuff in the database. As some endpoints update the database (and sometimes over multiple sql statements) I want to pass around the transaction as this embodies the connection I am using to update the database.

This makes sense. You just want a database connection pool (sqlx provides this) in your axum state so your handlers can get connections to the database.

To separate the axum stuff (parameters, urls and whatnot) from the actual database logic, I’ve first pulled out all the database interactions into separate functions. Because those functions are logically groups (e.g. stuff happening with invoices, others with contacts etc), I thought it was a good idea to create a “dao” struct (and agreed: my OO brain kicked in here which might be debatable). This would group the interactions for each logical domain into a short-lived data access struct.

Again, not sure what this DAO struct actually entails, but what I would do and have done in the past is just do exactly what you said before: “I want to pass around the transaction”. So I would make my functions take the Transaction struct from sqlx (IIRC it has some type parameters and a life time but you can use a type alias to make it less verbose) and then I would just use that transaction in the function to call SQL. If you have a function that needs access to the database but doesn’t need a transaction, you can just use a plain connection instead of a transaction.

To prevent passing around the transaction/connection, i wanted to pass that along during construction

I’m not sure what you mean with “pass along during construction” but in any case, why do you want to avoid passing the transaction/connection? I feel like that is exactly what you should do. That is what you need to do anyway. Rust favours explicitness and you need to pass the transaction/connection to functions for them to use it, so just pass it.

That’s not what I said. Read about the XY problem and then come back and explain what you actually want to achieve, and give some more information like code examples.

This screams of XY problem. You’ve gotten a new problem from using this method and you’re asking for help for that, but probably there is an underlying better solution that solves your actual use case without running into this problem at all.

most of the cost of [anything] goes to publishers, not the creators

My edit obviously. It does feel like that though. I pay Netflix, not the people making the movie. For games it is at least a bit better - I pay Valve (Steam) and the publisher but at least some of it goes directly to the devs. But it could be better still I suppose. But I’d honestly be okay if we got a Steam-like platform for series and movies where I could buy the ones I want without any subscriptions.

Uh, how? I mean you’d need to make it legal I feel like. But that’s never going to happen and I honestly don’t think that’s fair either. If piracy is legal, how would content creators actually be paid?

I get the sentiment but this is not really an option most of the time if you want to stick with lawful methods. For instance, I cannot watch most movies or TV series these days without a subscription to some service.

Getting fired with cause doesn’t come with severance

Yea this is fucked and needs to be fixed.

Why don’t they just keep working from home and get fired? Instead of having to quit themselves?

So as far as I gather, it’s still just as open source as before but you just can’t sell it on the Confluence marketplace? Seems fair.

Never forget to put glue on pizza, it really brings out a good flavour and makes the cheese all stringy!

It’s a test for the compiler which ensures that these legal yet extremely weird expressions continue to compile as the compiler is updated. So there is a purpose to the madness but it does still look pretty funny.

There’s a crate for it too: anymap2

Not exactly the same thing but this is still pretty funny. This is code that is technically 100% legal Rust but you should definitely never write such code 😅.

I mean… I feel like this could still apply 😅

To save it and save people a click to reddit:

Well in some languages other than English the sun is actually called “Sol”.

Frankly, all of your points sound quite ignorant. Syntax is literally just a matter of getting used to it. Comparing HashMap ergonomics doesn’t make sense, you should rather compare to struct construction. There are many good reasons for different string types and number types. There are good reasons not to bake in async. Rust documentation is in the code for a very good reason and it’s actually really nice to read docs like that (obviously read it on docs.rs, not in the code itself).

I could go on but there are answers to all of your specific qualms if you just bothered to look for yourself.