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.
(NOTE: This post is neither a complaint nor an invitation to complain about an individual's decision to stop providing volunteer labor in the form of maintaining his package.)
My online talk about how to speed up #Rust serialization with #serde by up to 2.25x 🚀
What to expect:
🙂 A simple example with JSON
🧐 How serialization in serde works
🛠️ Manually implementing the Serialize trait
🌟 Serialization with the newtype pattern
⏱️ Benchmarking with divan
🤔 Discussing the overhead of allocations
I've just tagged the 1.1 release of #Serde for #PHP. Now with improved value object support, so you can deserialize properties directly into their own validated value object!
I am quite proud of myself for having implemented a custom #serde Deserializer because the toml one wasn’t doing what I wanted. It cleans up my other code quite a bit. #rust#rustlang
Glad to see my 2 years old PR being merged into serde-bytes.
Now it supports [u8; N] !
As an added bonus the latest release also fixes an issue I raised a while ago. [serde(with = "serde_bytes")] now works even when the alloc feature is disabled.
This was a challenge and first time using #serde, so expected to take weeks (elapsed).
Thanks to the #Rust ecosystem, its awesome macros and serde's comprehensive type support it took a few days. 😱
More testing and tidying to do, but the really complex tricky stuff works.
To do this in the past would have been a large, complex, error prone task. I know because I've done it, save/load of a tree of complex structs including vectors, hashmaps and other library types.
I've done all the non #serde infrastructure needed to add save and restore checkpoints to #vdash which leaves... the core serialisation and de-serialisation of my safenode metrics structures, some of which are quite complex.
I'm hoping, and fairly confident that almost all of it will be able to use serde's built in type support. 🤞
Programming in #Rust is pretty awesome like that, but we'll see.
I'm about to venture into the wilds of #Rust#serialization for the next enhancement to #vdash and stumbled on an excellent article from @mo8it about improving serialization performance.
It happens to be a great introduction to using #serde as well as how to speed the whole process up considerably.
I've just tagged the 0.7.0 release of #Serde for #PHP, with a big set of bug fixes and new features. This is the last release before 1.0.0 comes out sometime in the next week.
Come see its official release presentation at @longhorn PHP! Tickets are still available.
Now that the #Serde issue is resolved by removing the binary, I want to thank @decathorpe again, not only for reporting the issue, but also for all his efforts in the #Rust and #Fedora communities ❤
For others: Please don't call things like this "drama" again. This is pushing back against mistakes that would affect the whole community. I love how much the community cares and that such problems are not ignored 🥰
We are not here to only get things done, we are building a future ❤
I've been doing #python these last days. And I hate it.
Runtime and env management is just as bad as Ruby. Dependency management is even worse than Ruby's.
No brackets, but indentation, means all the bracket pair features in vim, hardwired in my brain, don't work. Auto indentation isn't possible, bc brackets to derive the indentation from isn't there.
Aligning chained methods, large argument or param lists a pain, bc the indentation changes the meaning.
foo.bar() <> foo
.bar()
@Stark9837@berkes@radon@Python yeah I saw that too, did not get why it's so hard to make it optional. Security or not, what about cross-platform support for non-mainstream architectures? Do they build for every supported #rust target? I like #serde, but that's at the very least a weird move.
Based on the discussion here and in the PR, I've gone ahead and completed the PR to support null values in #Serde. If you use it currently, please review and make sure it doesn't break more than I already know it does. 🙂 #PHP I'll probably merge in a week or so, baring any contrary reviews.