*rubbing eyes* Anyone use "Rocket"?
Uncategorized
24
Posts
11
Posters
1
Views
-
@mcc As someone who has never tried Rust, I honestly can't tell if you're joking or not.
-
@mcc As someone who has never tried Rust, I honestly can't tell if you're joking or not.
@ryan This is literally a real thing in Rust but it's not called the wink operator. It does involve typing the characters <'_>.
Literally what it means: In Rust, every variable has a "lifetime" associated with it. Sometimes, you must explicitly tell the compiler what the lifetime is. But often, in this case, you can type <'_> which means "compiler, please figure out the lifetime for me". And often it succeeds.
-
*rubbing eyes* Anyone use "Rocket"?
The worst/most Ruby-like thing about Rocket is when you return a value from a Route function, you just kinda return… whatever datatype you want, and Rocket figures it out.
Unless it doesn't, and you have *no* idea what to return.
For a string, you return a String.
What do I return for bytes? It's not a string, it's a &[u8; 1335895] and it's not valid UTF-8. Do I return a rocket::response::ByteStream? That seems to be the correct answer but doesn't work
@mcc It seems that the `Stream` part (https://api.rocket.rs/v0.5/rocket/response/stream/) of the return type to be returned is actually supposed to be a type utilizing the `futures::stream::Stream` trait (https://docs.rs/futures/0.3.31/futures/stream/trait.Stream.html) internally, and all the wrapper types mentioned are basically "convenience wrappers" which implement the stream upon something else, and futhermore wrap it into a `rocket::responder::Responder` (https://api.rocket.rs/v0.5/rocket/response/trait.Responder), which furthermore also does the error handling, like a monad...
-
@mcc It seems that the `Stream` part (https://api.rocket.rs/v0.5/rocket/response/stream/) of the return type to be returned is actually supposed to be a type utilizing the `futures::stream::Stream` trait (https://docs.rs/futures/0.3.31/futures/stream/trait.Stream.html) internally, and all the wrapper types mentioned are basically "convenience wrappers" which implement the stream upon something else, and futhermore wrap it into a `rocket::responder::Responder` (https://api.rocket.rs/v0.5/rocket/response/trait.Responder), which furthermore also does the error handling, like a monad...
@mcc It feels like the easiest way to implement some custom borrowing strategy would be to "just" return a custom type that implements the `Responder` trait, and move most of the logic into that, at least as long as you don't need a complicated self-referential state machine to produce the output...
-
Update: .to_slice() was the magic solution. I need to remember to put this in my "things to try at random when Rust isn't working" along with typing <'_>.
@mcc Oh right, I keep forgetting Rust can't implicitly cast &[u8, N] to &[u8] for some reason
-
@fishidwardrobe I don't find a method named "pack" on String?
@mcc i beg your pardon. Array#pack -> String; String#unpack -> Array
-
@mcc i beg your pardon. Array#pack -> String; String#unpack -> Array
@fishidwardrobe I'm sorry: Do you understand that we are talking about the Rust programming language, and Ruby is mentioned because the Rocket library for Rust is heavily inspired by Ruby design philosophies? I now see I did not mention Rust specifically.
-
@mcc Oh right, I keep forgetting Rust can't implicitly cast &[u8, N] to &[u8] for some reason
-
undefined oblomov@sociale.network shared this topic
-
@fishidwardrobe I'm sorry: Do you understand that we are talking about the Rust programming language, and Ruby is mentioned because the Rocket library for Rust is heavily inspired by Ruby design philosophies? I now see I did not mention Rust specifically.
@mcc ah. no. shutting up now, sorry.
-
@mcc ah. no. shutting up now, sorry.
@fishidwardrobe I now understand the conversation again
Gli ultimi otto messaggi ricevuti dalla Federazione
-
For extra context: I'm saying this because I saw someone call my code “AI slop.”
-
Addio a Dave Farber. https://blog.quintarelli.it/2026/02/addio-a-dave-farber/
-
I think it's rude to just dismiss someone's work as “AI slop” simply because it uses some AI.
-
Alfa Romeo in formula uno: fine della storia.
Ottavio Tonti
Dal 1950 al 1988. La storia, raccontata da chi l'ha vissuta, di quando l'Alfa si ritirò definitivamente dalla Formula Uno.L'Alfa Benetton, le trattative con Toleman, Lotus, Williams e infine Ligier. L'acquisizione da parte della Fiat e il ritiro definitivo di Alfa Romeo anche solo come costruttore di motori.
-
@davew Vivaldi is a bit in your face about it, but they are staunchly NO AI.
-
I lunghi binari della guerra. Rete Transeuropea dei trasporti TEN-T
@anarchia
Crescono sempre più gli investimenti europei, come peraltro l’intensità delle fasi di lavorazione, riguardanti la definizione e messa a punto dei nove corridoi ferroviari della rete TEN-T. Come riportato nel primo bollettino dei Ferrovier3 contro la guerra, il progetto della...Vedi
-
@eniko holy smokes that looks really good actually
-
Hi, new followers! Seems like a good time for a re-introduction.
I'm Hong Minhee (洪 民憙), a software engineer based in Seoul. My pronouns are they/them.
I build tools for the fediverse. Fedify is an ActivityPub server framework in TypeScript, Hollo is a single-user microblogging server (what you're reading this on), and BotKit is a framework for making ActivityPub bots. I care a lot about making federation more accessible to developers, which, as my recent JSON-LD rant probably made clear, sometimes means wrestling with parts of the spec I have complicated feelings about.
I'm a free/open source software person through and through, and a socialist, which informs how I think about tech. Lately I've been thinking a lot about LLMs. My position is probably not what you'd expect from either camp: I think the problem isn't the technology itself but the enclosure of the commons. I wrote about this at length here if you're curious: Histomat of F/OSS: We should reclaim LLMs, not reject them.
Outside of software, I have a long-running interest in CJK languages and writing systems. I'm always happy to talk about Chinese characters, Korean orthography, or the weird corners of Unicode where these things intersect.
Nice to meet you all, and thanks for following.
