Nobody ever got fired for using a struct

Rust struct serialization problem caused by many nullable SQL columns.

When a few variables belong together, we put them in a struct. Programmers do this automatically without thinking about it much. And most of the time it's the right choice. Structs are simple, fast, and predictable. But once in a while they break down. This is the story of one of those cases. How it started One of our customers reported a strange performance problem. A new use case processed about the same amount of data as their existing pipelines, but it ran much slower. That was unusual. Our engine normally keeps up with the data customers send. So we felt compelled to take a closer look. H

saved by

• Sam B

related reading

• An Example Program Using Structs - The Rust Programming Languagedoc.rust-lang.org
• A half-hour to learn Rustfasterthanli.me
• The Lost Art of Structure Packingcatb.org
• Defining an Enum - The Rust Programming Languagedoc.rust-lang.org
• NYSRGnotes.ekzhang.com
• How many options fit into a boolean? | MOND←TECH MAGAZINEherecomesthemoon.net
• Defining and Instantiating Structs - The Rust Programming Languagedoc.rust-lang.org
• Rust Optimization.md · GitHubgist.github.com
• Against SQLscattered-thoughts.net
• Rust Language Cheat Sheetcheats.rs
• Struct padding in C++ - Stack Overflowstackoverflow.com
• Item 7: Use builders for complex types - Effective Rustlurklurk.org