@davedelong, they mention @rust #Serde framework, so they are not too far from your idea.
“The Serde ecosystem consists of data structures that know how to serialize and deserialize themselves along with data formats that know how to serialize and deserialize other things.”
New Rust crate alert: eserde! 
Tired of getting just one error at a time when deserializing with `serde`? `eserde` (built on top of `serde`) reports multiple errors at once, making API debugging way smoother.
Read @algo_luca ’s deep dive on why we built it & how to use it 
https://mainmatter.com/blog/2025/02/13/eserde/
Unlocking Data Efficiency: How Rust Interning Achieved 2000x Compression on RATP Transport Data
In a remarkable weekend project, a developer leveraged Rust's interning design pattern to compress a massive dataset from Paris' public transport network, achieving an astounding 2000x reduction in si...
If you're in King's Hall at #RustNationUK, I found the crate Adam Harvey told us not to post on the social media about!
Unlocking the Power of Refinement Types in Rust with the 'refined' Library
The newly released 'refined' library for Rust offers developers a robust way to implement refinement types, enhancing type safety and reducing bugs. This innovative approach not only improves document...
Ok, a (half a) day of satisfaction was enough.
Everything works well still, but there is room for optimization. Not the optimization of #rust code, but of the RMI structure itself. There needs to be a family of RMI request structs, and I'm thankful to #rust for not providing me with #oop stuff, because I really don't need going down that rabbithole.
Containment will suffice, I'm just eager to see what #serde will have to say about it...
I see I'm not the only one who pronounces #serde in a way that rhymes with “merde”.
https://github.com/kdl-org/kdl-rs/pull/83
the work has begun to add #serde support to #kdl rs!
It'll take me a bit, but the parser refactor that'll let me do this is going well.
anyway this is all very exciting because I think not being able to use serde has tbh been a huge blocker for folks adopting kdl in Rust
EDIT: answer found, please see downthread
Coding question: is there something for #python like #serde where the serialized version of the data can be a format you define, not Just Fucking JSON
Before you ask: no I can't change the format to JSON, it's hardcoded into this DVD player I have. Yes, you read that right.
Great article by Alisa Sireneva!
https://purplesyringa.moe/blog/i-sped-up-serde-json-strings-by-20-percent/
Rust's serde should really support default literals!
Read more: https://serde.rs/attr-default.html
Tracking issue: https://github.com/serde-rs/serde/issues/368
Написать X-docker-isolation-provider сложно — но не невозможно
Вы когда-нибудь чувствовали себя пионерами? Вот именно так я себя и ощущал, когда писал docker-isolation-provider для платформы ассоциативного программирования Deep . Все было так: в один прекрасный день у нас на платформе связей решили - было бы славно портировать нашего бота в Deep . А для этого нужно было написать так называемые провайдеры . Провайдеры нужны лишь для одной цели - дать возможность пользователю выполнять пользовательские хэндлеры на любом языке. Тогда я просто подумал, что было бы неплохо помочь парням, которые вероятно Rust никогда в жизни не видели . Ох, как же я тогда ошибался…
TPM2 command encoding with #bincode and #serde:
let options = DefaultOptions::new()
.with_fixint_encoding()
.with_big_endian();
buf.extend(&options.serialize(&(Tag::NoSessions as u16)).unwrap());
buf.extend(&options.serialize(&22_u32).unwrap());
buf.extend(
&options
.serialize(&(CommandCode::GetCapability as u32))
.unwrap(),
);
buf.extend(&options.serialize(&(Capability::Handles as u32)).unwrap());
buf.extend(&options.serialize(&HR_PERSISTENT).unwrap());
buf.extend(&options.serialize(&1_u32).unwrap());
Form data (x-www-form-urlencoded) support in #Axum is a bit disappointing. It uses #serde’s serde_urlencoded underneath, which in principle is fine. But the problem is that HTML forms don’t let you *not send* a value, which makes the whole thing useless with optional fields. You can set a field in a form to not be required and send an empty value (`?foo&bar=3&…` or `?foo=&bar=3&…` for empty `foo`) but then serde treats it as a present empty string and fails deserialization.
I've just tagged a new release of Crell/Serde, version 1.2.
This release includes support for Unix timestamps, makes TypeFields more flexible and customizable, and fixes an issue with handling null values. Note that the latter fix has a very small BC break that only impacts a select number of custom Importers, so odds are you won't notice.
Get it while it's hot!
And I’ve thrown out that solution again. Instead of messing with serde::Deserialize which never quite works as it should, I’ve decided to extend the API and support flattened structs properly. I’ve added my solution to this already much too long thread where lots of people spent lots of time trying to make things somehow work with Serde’s APIs.
Any #rustlang #serde experts out there willing to help me out with a "Deserializer adapter" for skipping duplicate JSON keys when deserializing using serde_json? https://users.rust-lang.org/t/serde-how-to-create-a-deserializer-adapter-to-ignore-duplicate-fields-in-json-data/112252
I finally managed to create a serde::Deserialize implementation that would support flatten and deny_unknown_fields at the same time. The issue was mostly how the Serde API makes this task difficult for no good reason from what I can tell.
I sort of see why it has to be static strings everywhere, but why static slices as well? That’s an implementation detail of the default implementation and IMHO not actually required anywhere. And why is it so hard to get to the list of fields supported by an implementation?
I guess this use case was never a priority, but configuration files where a typo in a field name won’t be recognized are a major PITA…
Кратко про Serde в Rust
Serde — это высокопроизводительная библиотека для сериализации и десериализации данных в Rust. Она поддерживает различные форматы данных, включая JSON , YAML , TOML , BSON и многие другие. В этой статье рассмотрим основы Serde в Rust.
