commit | 6557ec3e4a7b431f649322ad555a972d8d690e6f | [log] [tgz] |
---|---|---|
author | Joel Galenson <jgalenson@google.com> | Tue Aug 24 18:24:02 2021 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Tue Aug 24 18:24:02 2021 +0000 |
tree | 42b40c6ce8ce28f25eff5ba557decc661fcab540 | |
parent | 4ae1c80a924b1abcebac8ee43a0fb217f67767b3 [diff] | |
parent | 4b112f110dfba7c24fdb7dadb75445ac4014b015 [diff] |
Update TEST_MAPPING am: 4b112f110d Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/serde/+/1806168 Change-Id: Id51e5d435fa6c7c25f31ff5c869477ec3a21013a
Serde is a framework for serializing and deserializing Rust data structures efficiently and generically.
You may be looking for:
#[derive(Serialize, Deserialize)]
[dependencies] # The core APIs, including the Serialize and Deserialize traits. Always # required when using Serde. The "derive" feature is only required when # using #[derive(Serialize, Deserialize)] to make Serde work with structs # and enums defined in your crate. serde = { version = "1.0", features = ["derive"] } # Each data format lives in its own crate; the sample code below uses JSON # but you may be using a different one. serde_json = "1.0"
use serde::{Serialize, Deserialize}; #[derive(Serialize, Deserialize, Debug)] struct Point { x: i32, y: i32, } fn main() { let point = Point { x: 1, y: 2 }; // Convert the Point to a JSON string. let serialized = serde_json::to_string(&point).unwrap(); // Prints serialized = {"x":1,"y":2} println!("serialized = {}", serialized); // Convert the JSON string back to a Point. let deserialized: Point = serde_json::from_str(&serialized).unwrap(); // Prints deserialized = Point { x: 1, y: 2 } println!("deserialized = {:?}", deserialized); }
Serde is one of the most widely used Rust libraries so any place that Rustaceans congregate will be able to help you out. For chat, consider trying the #general or #beginners channels of the unofficial community Discord, the #rust-usage channel of the official Rust Project Discord, or the #general stream in Zulip. For asynchronous, consider the [rust] tag on StackOverflow, the /r/rust subreddit which has a pinned weekly easy questions post, or the Rust Discourse forum. It's acceptable to file a support issue in this repo but they tend not to get as many eyes as any of the above and may get closed without a response after some time.