Some people before #LLMs
"But writing #documentation is so time-consuming. We have no time for that!"
"We won't adopt #Rust as our service is not performance-critical."
----------------
The same people after LLMs:
"We need some more docs over here... and please update that SKILL.md. Otherwise, how should our LLM navigate our codebase and know what to do?"
"#RustLang is awesome! LLMs make way fewer errors now with strict types!"
Just insane!
Is your company currently hiring for a role that includes using Rust?
Reply with a link to the opening and any relevant context.
If you're not, we'd appreciate a repost for visibility
Hi rustaceans. I'm hitting a wall with this life time error where I think lifetimes should not play a role.
Why is the lifetime of a trait's associated type even in question when defining a generic axum handler? The type parameter is not the type of an argument, it's not contained in a future and it's not the type of a return value. I'm drawing a complete blank and your insight or boosts are much appreciated!
I'm hitting a wall with a weird-to-me compiler error. When creating a generic axum handler function, it requires that the type parameters be Send + Sync + 'static, even in examples where they are simple associated types that never need to be sent between threads. I found a minimum reproducible example where the type parameter isn't even ever used: use std::sync::Arc; use axum::{Router, extract::State, response::IntoResponse, routing::get}; trait Greeter: Send + Sync { type GreetType; ...
RE: https://fosstodon.org/@rustnl/116119445480765544
Warning: the end of this talk might be unreachable!
Is your company currently hiring for a role that includes using Rust?
Reply with a link to the opening and any relevant context.
If you're not, we'd appreciate a repost for visibility
Jan 
Rust Bytes
tusharhero
Karpi
Tubemeister
Terts Diepraam