#serde — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #serde, aggregated by home.social.
-
Wait what, #serde doesn't contain any slop commits, while not excplicitly forbidding it..?? Is this just a coincidence, that sloppers just...forgot about that critical piece of rust ecosystem even exist?????
-
Wait what, #serde doesn't contain any slop commits, while not excplicitly forbidding it..?? Is this just a coincidence, that sloppers just...forgot about that critical piece of rust ecosystem even exist?????
-
Wait what, #serde doesn't contain any slop commits, while not excplicitly forbidding it..?? Is this just a coincidence, that sloppers just...forgot about that critical piece of rust ecosystem even exist?????
-
Wait what, #serde doesn't contain any slop commits, while not excplicitly forbidding it..?? Is this just a coincidence, that sloppers just...forgot about that critical piece of rust ecosystem even exist?????
-
Wait what, #serde doesn't contain any slop commits, while not excplicitly forbidding it..?? Is this just a coincidence, that sloppers just...forgot about that critical piece of rust ecosystem even exist?????
-
Как я писал генератор TypeScript-биндингов для Tauri
В Tauri фронтенд дёргает Rust-команды через invoke("get_user", { userId: 42 }) — строка, объект, никакой проверки типов. После очередного вечера, убитого на расхождение snake_case и camelCase, я написал генератор, который превращает Rust-команды и serde-типы в готовые TypeScript-файлы — без аннотаций и правок в коде приложения. Под катом — почему генерировать надо не то, что написано в коде, а то, что serde реально шлёт по проводу; как я выпустил три релиза за один день, воюя с макросами; и при чём тут юникод-эскейпы в TOML на Windows.
https://habr.com/ru/articles/1048060/
#tauri #rust #typescript #кодогенерация #биндинги #serde #ipc #cli
-
Как я писал генератор TypeScript-биндингов для Tauri
В Tauri фронтенд дёргает Rust-команды через invoke("get_user", { userId: 42 }) — строка, объект, никакой проверки типов. После очередного вечера, убитого на расхождение snake_case и camelCase, я написал генератор, который превращает Rust-команды и serde-типы в готовые TypeScript-файлы — без аннотаций и правок в коде приложения. Под катом — почему генерировать надо не то, что написано в коде, а то, что serde реально шлёт по проводу; как я выпустил три релиза за один день, воюя с макросами; и при чём тут юникод-эскейпы в TOML на Windows.
https://habr.com/ru/articles/1048060/
#tauri #rust #typescript #кодогенерация #биндинги #serde #ipc #cli
-
Как я писал генератор TypeScript-биндингов для Tauri
В Tauri фронтенд дёргает Rust-команды через invoke("get_user", { userId: 42 }) — строка, объект, никакой проверки типов. После очередного вечера, убитого на расхождение snake_case и camelCase, я написал генератор, который превращает Rust-команды и serde-типы в готовые TypeScript-файлы — без аннотаций и правок в коде приложения. Под катом — почему генерировать надо не то, что написано в коде, а то, что serde реально шлёт по проводу; как я выпустил три релиза за один день, воюя с макросами; и при чём тут юникод-эскейпы в TOML на Windows.
https://habr.com/ru/articles/1048060/
#tauri #rust #typescript #кодогенерация #биндинги #serde #ipc #cli
-
via @dotnet : VSTest is Removing its Newtonsoft.Json Dependency
https://ift.tt/PYIZ0Ny
#VSTest #NewtonsoftJson #SystemTextJson #JSONite #dotnet11 #VisualStudio #VS2024 #dotnetTest #TestExplorer #NuGet #SecurityUpdate #SerDe #JsonDependency #BreakingChange #DotNe… -
via @dotnet : VSTest is Removing its Newtonsoft.Json Dependency
https://ift.tt/PYIZ0Ny
#VSTest #NewtonsoftJson #SystemTextJson #JSONite #dotnet11 #VisualStudio #VS2024 #dotnetTest #TestExplorer #NuGet #SecurityUpdate #SerDe #JsonDependency #BreakingChange #DotNe… -
via @dotnet : VSTest is Removing its Newtonsoft.Json Dependency
https://ift.tt/PYIZ0Ny
#VSTest #NewtonsoftJson #SystemTextJson #JSONite #dotnet11 #VisualStudio #VS2024 #dotnetTest #TestExplorer #NuGet #SecurityUpdate #SerDe #JsonDependency #BreakingChange #DotNe… -
via @dotnet : VSTest is Removing its Newtonsoft.Json Dependency
https://ift.tt/PYIZ0Ny
#VSTest #NewtonsoftJson #SystemTextJson #JSONite #dotnet11 #VisualStudio #VS2024 #dotnetTest #TestExplorer #NuGet #SecurityUpdate #SerDe #JsonDependency #BreakingChange #DotNe… -
via @dotnet : VSTest is Removing its Newtonsoft.Json Dependency
https://ift.tt/PYIZ0Ny
#VSTest #NewtonsoftJson #SystemTextJson #JSONite #dotnet11 #VisualStudio #VS2024 #dotnetTest #TestExplorer #NuGet #SecurityUpdate #SerDe #JsonDependency #BreakingChange #DotNe… -
@simontatham greatness averted, we could have had #derive #async_trait #strum #tokio #command #cfg #serde
-
@simontatham greatness averted, we could have had #derive #async_trait #strum #tokio #command #cfg #serde
-
@simontatham greatness averted, we could have had #derive #async_trait #strum #tokio #command #cfg #serde
-
@simontatham greatness averted, we could have had #derive #async_trait #strum #tokio #command #cfg #serde
-
@simontatham greatness averted, we could have had #derive #async_trait #strum #tokio #command #cfg #serde
-
Today, I once again wake up worrying about #Rust 's future.
Why is a shitbag such as #dtolnay still allowed to single-handedly maintain fundamental libraries for the ecosystem? Why is he part of Library API team? How is he not permabanned for single-handedly permanently damaging Rust by killing off comptime reflection over his racism? How is he not permabanned for the power play he attempted to pull with his "RFC" after pushing pre-compiled binary to serde without notice? Why are MIC companies routinely tolerated at Rust conventions? Why does no one talk about it, despite the problems not being solved? Has #Ruby takeover taught people nothing? Will Rust survive another year without turning into #fashtech?
So many questions. I think about them every time I use Rust, which is often.
Apropos of nothing.
-
Today, I once again wake up worrying about #Rust 's future.
Why is a shitbag such as #dtolnay still allowed to single-handedly maintain fundamental libraries for the ecosystem? Why is he part of Library API team? How is he not permabanned for single-handedly permanently damaging Rust by killing off comptime reflection over his racism? How is he not permabanned for the power play he attempted to pull with his "RFC" after pushing pre-compiled binary to serde without notice? Why are MIC companies routinely tolerated at Rust conventions? Why does no one talk about it, despite the problems not being solved? Has #Ruby takeover taught people nothing? Will Rust survive another year without turning into #fashtech?
So many questions. I think about them every time I use Rust, which is often.
Apropos of nothing.
-
Today, I once again wake up worrying about #Rust 's future.
Why is a shitbag such as #dtolnay still allowed to single-handedly maintain fundamental libraries for the ecosystem? Why is he part of Library API team? How is he not permabanned for single-handedly permanently damaging Rust by killing off comptime reflection over his racism? How is he not permabanned for the power play he attempted to pull with his "RFC" after pushing pre-compiled binary to serde without notice? Why are MIC companies routinely tolerated at Rust conventions? Why does no one talk about it, despite the problems not being solved? Has #Ruby takeover taught people nothing? Will Rust survive another year without turning into #fashtech?
So many questions. I think about them every time I use Rust, which is often.
Apropos of nothing.
-
Today, I once again wake up worrying about #Rust 's future.
Why is a shitbag such as #dtolnay still allowed to single-handedly maintain fundamental libraries for the ecosystem? Why is he part of Library API team? How is he not permabanned for single-handedly permanently damaging Rust by killing off comptime reflection over his racism? How is he not permabanned for the power play he attempted to pull with his "RFC" after pushing pre-compiled binary to serde without notice? Why are MIC companies routinely tolerated at Rust conventions? Why does no one talk about it, despite the problems not being solved? Has #Ruby takeover taught people nothing? Will Rust survive another year without turning into #fashtech?
So many questions. I think about them every time I use Rust, which is often.
Apropos of nothing.
-
Today, I once again wake up worrying about #Rust 's future.
Why is a shitbag such as #dtolnay still allowed to single-handedly maintain fundamental libraries for the ecosystem? Why is he part of Library API team? How is he not permabanned for single-handedly permanently damaging Rust by killing off comptime reflection over his racism? How is he not permabanned for the power play he attempted to pull with his "RFC" after pushing pre-compiled binary to serde without notice? Why are MIC companies routinely tolerated at Rust conventions? Why does no one talk about it, despite the problems not being solved? Has #Ruby takeover taught people nothing? Will Rust survive another year without turning into #fashtech?
So many questions. I think about them every time I use Rust, which is often.
Apropos of nothing.
-
@asonix But that sounds right like what @KingmaYpe suggested:
enum FieldString { Quoted(String), Bare(String) }
The hard part is probably to send those through serde's interface, right? You could probably recognize the names in your serializer in serialize_newtype_variant and then emit possibly-quotes and the inner value.
Whether that is good use of #Serde, I do not know. -
@asonix But that sounds right like what @KingmaYpe suggested:
enum FieldString { Quoted(String), Bare(String) }
The hard part is probably to send those through serde's interface, right? You could probably recognize the names in your serializer in serialize_newtype_variant and then emit possibly-quotes and the inner value.
Whether that is good use of #Serde, I do not know. -
@asonix But that sounds right like what @KingmaYpe suggested:
enum FieldString { Quoted(String), Bare(String) }
The hard part is probably to send those through serde's interface, right? You could probably recognize the names in your serializer in serialize_newtype_variant and then emit possibly-quotes and the inner value.
Whether that is good use of #Serde, I do not know. -
@asonix But that sounds right like what @KingmaYpe suggested:
enum FieldString { Quoted(String), Bare(String) }
The hard part is probably to send those through serde's interface, right? You could probably recognize the names in your serializer in serialize_newtype_variant and then emit possibly-quotes and the inner value.
Whether that is good use of #Serde, I do not know. -
@asonix But that sounds right like what @KingmaYpe suggested:
enum FieldString { Quoted(String), Bare(String) }
The hard part is probably to send those through serde's interface, right? You could probably recognize the names in your serializer in serialize_newtype_variant and then emit possibly-quotes and the inner value.
Whether that is good use of #Serde, I do not know. -
RE: https://masto.asonix.dog/@asonix/115487539746688367
quooting to improve hashtag visibility
serde-knower-abouters please help
-
RE: https://masto.asonix.dog/@asonix/115487539746688367
quooting to improve hashtag visibility
serde-knower-abouters please help
-
RE: https://masto.asonix.dog/@asonix/115487539746688367
quooting to improve hashtag visibility
serde-knower-abouters please help
-
Can anyone point me to a serde data format that uses multiple distinct string representations?
Or a serde data format that isn't self-describing?
Or a serde data format that has distinct "top level" types that are different from inner types
Unfortunately I'm implementing a data format that has all of these things and it's making serde hard
-
Can anyone point me to a serde data format that uses multiple distinct string representations?
Or a serde data format that isn't self-describing?
Or a serde data format that has distinct "top level" types that are different from inner types
Unfortunately I'm implementing a data format that has all of these things and it's making serde hard
-
Can anyone point me to a serde data format that uses multiple distinct string representations?
Or a serde data format that isn't self-describing?
Or a serde data format that has distinct "top level" types that are different from inner types
Unfortunately I'm implementing a data format that has all of these things and it's making serde hard
-
what if we kissed at the Serde documentation site? implementing Serialize and Deserialize f... - 10/14/2025, 11:26:31 PM
-
what if we kissed at the Serde documentation site? implementing Serialize and Deserialize f... - 10/14/2025, 11:26:31 PM
-
serde shenanigans! implementing Serialize and Deserialize for RFC8941 - 10/11/2025, 12:40:19 AM
-
serde shenanigans! implementing Serialize and Deserialize for RFC8941 - 10/11/2025, 12:40:19 AM
-
I feel like I'm always using serde incorrectly:
it's far too easy to conflate the abstract model representation and the serialized representation for some data. (ie: just stick #[derive(Deserialize)] everywhere and call it a day). But if I make the serialization structs separate, the model instantly becomes full of lifetimes and references and ugh.... messy.
Is there a good writeup somewhere for like... good design while using serde?
-
I feel like I'm always using serde incorrectly:
it's far too easy to conflate the abstract model representation and the serialized representation for some data. (ie: just stick #[derive(Deserialize)] everywhere and call it a day). But if I make the serialization structs separate, the model instantly becomes full of lifetimes and references and ugh.... messy.
Is there a good writeup somewhere for like... good design while using serde?
-
I feel like I'm always using serde incorrectly:
it's far too easy to conflate the abstract model representation and the serialized representation for some data. (ie: just stick #[derive(Deserialize)] everywhere and call it a day). But if I make the serialization structs separate, the model instantly becomes full of lifetimes and references and ugh.... messy.
Is there a good writeup somewhere for like... good design while using serde?
-
I feel like I'm always using serde incorrectly:
it's far too easy to conflate the abstract model representation and the serialized representation for some data. (ie: just stick #[derive(Deserialize)] everywhere and call it a day). But if I make the serialization structs separate, the model instantly becomes full of lifetimes and references and ugh.... messy.
Is there a good writeup somewhere for like... good design while using serde?
-
I feel like I'm always using serde incorrectly:
it's far too easy to conflate the abstract model representation and the serialized representation for some data. (ie: just stick #[derive(Deserialize)] everywhere and call it a day). But if I make the serialization structs separate, the model instantly becomes full of lifetimes and references and ugh.... messy.
Is there a good writeup somewhere for like... good design while using serde?
-
🤦♂️ Someone thought it was a good idea to mix Rust's crusty rigor with Python's whimsical magic, using #Serde as the glue. Because nothing screams 'user-friendly' like making #Rust dance to Python's tune through a #serialization library! 🎻✨
https://ohadravid.github.io/posts/2025-05-serde-reflect/ #Python #programming #userfriendly #HackerNews #ngated -
🤦♂️ Someone thought it was a good idea to mix Rust's crusty rigor with Python's whimsical magic, using #Serde as the glue. Because nothing screams 'user-friendly' like making #Rust dance to Python's tune through a #serialization library! 🎻✨
https://ohadravid.github.io/posts/2025-05-serde-reflect/ #Python #programming #userfriendly #HackerNews #ngated -
🤦♂️ Someone thought it was a good idea to mix Rust's crusty rigor with Python's whimsical magic, using #Serde as the glue. Because nothing screams 'user-friendly' like making #Rust dance to Python's tune through a #serialization library! 🎻✨
https://ohadravid.github.io/posts/2025-05-serde-reflect/ #Python #programming #userfriendly #HackerNews #ngated -
🤦♂️ Someone thought it was a good idea to mix Rust's crusty rigor with Python's whimsical magic, using #Serde as the glue. Because nothing screams 'user-friendly' like making #Rust dance to Python's tune through a #serialization library! 🎻✨
https://ohadravid.github.io/posts/2025-05-serde-reflect/ #Python #programming #userfriendly #HackerNews #ngated -
🤦♂️ Someone thought it was a good idea to mix Rust's crusty rigor with Python's whimsical magic, using #Serde as the glue. Because nothing screams 'user-friendly' like making #Rust dance to Python's tune through a #serialization library! 🎻✨
https://ohadravid.github.io/posts/2025-05-serde-reflect/ #Python #programming #userfriendly #HackerNews #ngated -
A Rust API Inspired by Python, Powered by Serde
https://ohadravid.github.io/posts/2025-05-serde-reflect/
#HackerNews #Rust #Python #API #Serde #Programming #Languages
-
A Rust API Inspired by Python, Powered by Serde
https://ohadravid.github.io/posts/2025-05-serde-reflect/
#HackerNews #Rust #Python #API #Serde #Programming #Languages
-
A Rust API Inspired by Python, Powered by Serde
https://ohadravid.github.io/posts/2025-05-serde-reflect/
#HackerNews #Rust #Python #API #Serde #Programming #Languages
-
A Rust API Inspired by Python, Powered by Serde
https://ohadravid.github.io/posts/2025-05-serde-reflect/
#HackerNews #Rust #Python #API #Serde #Programming #Languages
-
I always wondered why I always found the #serde deserialization API (from a deserializer implementer's perspective) so hard to keep straight in my head. It dawned on me today: it's because it's a 3-body problem. You have 3 types to think about: Deserialize, Deserializer and Visitor.
-
I always wondered why I always found the #serde deserialization API (from a deserializer implementer's perspective) so hard to keep straight in my head. It dawned on me today: it's because it's a 3-body problem. You have 3 types to think about: Deserialize, Deserializer and Visitor.
-
I always wondered why I always found the #serde deserialization API (from a deserializer implementer's perspective) so hard to keep straight in my head. It dawned on me today: it's because it's a 3-body problem. You have 3 types to think about: Deserialize, Deserializer and Visitor.
-
I always wondered why I always found the #serde deserialization API (from a deserializer implementer's perspective) so hard to keep straight in my head. It dawned on me today: it's because it's a 3-body problem. You have 3 types to think about: Deserialize, Deserializer and Visitor.
-
I always wondered why I always found the #serde deserialization API (from a deserializer implementer's perspective) so hard to keep straight in my head. It dawned on me today: it's because it's a 3-body problem. You have 3 types to think about: Deserialize, Deserializer and Visitor.
-
@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.”
-
@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.”
-
@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.”