A different serde

[@AlJohri]

22:29 I think the original term “splat” comes from ruby/perl.

[@LDVSoft]

Oooh, nice! It also somewhat mirrors the reflection research.

[@Dygear]

I pronounce it serde, not serde *flips table*. LOL

[@theevilcottonball]

Sir D. using serde on a serious saturday.

[@remrevo3944]

13:40 There is not only a deserialize in_place method (about which I hadn't heard before), but there also is DeserializeSeed thingy, which might allow directly serializing into a `&mut [_]`. (Though IIRC that is a bit more annoying to set up and might need a manual implementation.)

[@sdr_pod]

👀

[@remrevo3944]

@@sdr_pod I actually learned about it in a still work-in-progress attempt to implement an async-await compatible serde-Deserializer. It works the same like the standard `Deserialize` trait, just that it lets you seed the deserialization process with a custom piece of data, which then can be used to construct the visitor. For my usecase that can be used for keeping datatype specific state even after the deserializer errors out with Err::Pending.

[@macroscalequantumsys]

39:00 postcard-ebpf when? :D

[@ColorfirePluma]

A lot of the links in the description include the closing parenthesis which are leading them to 404 pages

[@sdr_pod]

Thanks for the catch! Removed all parentheses, they should all work now :)

[@MattHudsonAtx]

Interesting. I was looking at CBOR for this.

[@sdr_pod]

We talk about CBOR (and self-describing vs non-self-describing formats) in general here: kzbin.info/www/bejne/bnq3fJyCoZyAaZY

[@mateusvmv]

memcpy is still the best serializer 😛

[@theevilcottonball]

Nope its mmap :-)

[@jamestjw97]

I wonder what tool/app he used to make this presentation, its pretty

[@sdr_pod]

It's just regular Keynote on MacOS!

[@jamestjw97]

@@sdr_pod cool! I loved the look of the presentation btw :)

[@TheLucanicLord]

There would be a slope up thing on the e if it was serdAY.

[@skeleton_craftGaming]

casting any type to char* is well defined C++ ... And everyone uses x86-64 right? [N]RVO isnt guaranteed by LLVM? Thats odd given that the c++ standard does and LLVM is a C[++] [and swift can't forget swift or Tim Cook will personally come after me] compiler first and foremost

[@hemerythrin]

RVO changes the behavior of your program, by optimizing out a constructor call, *even* if that constructor has side effects! That's not something the LLVM backend could (or should) do.

[@bianchialex]

I’m not convinced this isn’t an AI conversation

[@MattHudsonAtx]

It's missing the shite pronunciations, weird pauses, and other diction errors

[@sdr_pod]

Man, that would make all the time and effort we spend writing, recording, and editing these podcasts seem kinda silly, huh?

[@funkdefied1]

@@sdr_podtake it as a compliment. Your voices and audio quality have a professional sound. The content clearly isn’t vapid gibberish like an AI conversation would be.

[@justapotota4330]

@@funkdefied1every AI-dubbed video I’ve heard has awful audio quality