#tsv #serialization #serde #table #csv


tsv (tab-seperated-values) data format for serde (serialization/deserialization)

2 releases

Uses old Rust 2015

0.1.1 Sep 26, 2018
0.1.0 Aug 16, 2018

#1600 in Parser implementations

36 downloads per month

MIT license

1.5K SLoC

The tsv project introduces a new format for data serialization/deserialization, which is text-based and deals with tabular data.

The problem

At serde's point of view, the classic tsv is only applicable to the schema of (a sequence of) a struct composed of primitives( integer, floats, strings etc). The specification has to be extended to allow arbitrary schemas, such as a struct of a struct.

The solution

This project extends the spec by placing sequences in columns. See tsv-spec.txt for specification. It uses serde crate for serialization/deserialization, and reflection crate for generating column names and dealing with enums.


If you impl Serialize/Deserialize for your types to tell serde they are sequences/maps, do make sure their schemata() and Vec::schemata()/HashMap::schemata() are isomorphic.


  1. Simple. The only requirement for end users to use tsv files is to understand what a table is. It is deadly simple as a configuration file format for non-technical users.

  2. Available. You can use Microsoft Excel, OpenOffice/LibreOffie Calc and text editors that support elastic tabstops to view/edit tsv files. And it is easy to write tsv by hand if you have read all the 63 lines of the spec.


  1. Not efficiency-oriented.

  2. Not self-descripting.


Under MIT.


A cargo configuration file written in tsv format could look like the following table( with spaces replacing tabs ):

package                         lib             value    
name    version authors keyword macro   name    Version Path
tsv     0.1.0   oooutlk tsv     X       serde   1.0
                        tab             trees           ~/trees

See serialization example and deserialization example.


~55K SLoC