diff options
Diffstat (limited to 'users/wpcarro/scratch/rust/json/src/main.rs')
-rw-r--r-- | users/wpcarro/scratch/rust/json/src/main.rs | 37 |
1 files changed, 37 insertions, 0 deletions
diff --git a/users/wpcarro/scratch/rust/json/src/main.rs b/users/wpcarro/scratch/rust/json/src/main.rs new file mode 100644 index 000000000000..b810cfa77fe6 --- /dev/null +++ b/users/wpcarro/scratch/rust/json/src/main.rs @@ -0,0 +1,37 @@ +use serde_json::json; + +// From the serde_json docs: +// +// > There are three common ways that you might find yourself needing to work with +// > JSON data in Rust. +// > +// > 1. As text data. An unprocessed string of JSON data that you receive on an +// > HTTP endpoint, read from a file, or prepare to send to a remote server. +// > 2. As an untyped or loosely typed representation. Maybe you want to check +// > that some JSON data is valid before passing it on, but without knowing +// > the structure of what it contains. Or you want to do very basic +// > manipulations like insert a key in a particular spot. +// > 3. As a strongly typed Rust data structure. When you expect all or most of +// > your data to conform to a particular structure and want to get real work +// > done without JSON’s loosey-goosey nature tripping you up. +// +// So let's take a look at all three... + +// 1) Reading/writing from/to plain text. +// TL;DR: +// - read: serde_json::from_str(data) +// - write: x.to_string() +fn one() { + let data = json!({ + "fname": "William", + "lname": "Carroll", + "age": 30, + }) + .to_string(); + + println!("result: {:?}", data); +} + +fn main() { + one() +} |