#serialization #deserialization #introspection

savefile

Simple, convenient, fast, versioned, binary serialization/deserialization library. Works on stable rust, but provides much better performance with nightly.

38 releases

0.13.0 May 1, 2023
0.12.0 Jan 19, 2023
0.11.0 Oct 4, 2022
0.10.1 Feb 15, 2022
0.2.7 Mar 28, 2018

#80 in Encoding

Download history 189/week @ 2023-02-02 309/week @ 2023-02-09 358/week @ 2023-02-16 252/week @ 2023-02-23 258/week @ 2023-03-02 238/week @ 2023-03-09 98/week @ 2023-03-16 138/week @ 2023-03-23 135/week @ 2023-03-30 129/week @ 2023-04-06 206/week @ 2023-04-13 215/week @ 2023-04-20 276/week @ 2023-04-27 240/week @ 2023-05-04 232/week @ 2023-05-11 207/week @ 2023-05-18

1,003 downloads per month
Used in 4 crates

MIT/Apache

215KB
4.5K SLoC

Introduction to Savefile

Savefile is a library to effortlessly serialize rust structs and enums. It uses an efficient binary format. It can serialize to anything implementing the Write trait, and then deserialize from anything implementing the Read trait. This means that savefile can be used to easily save in-memory data structures to disk for persistent storage.

You may ask what savefile brings to the table that serde doesn't already do better. The answer is: Not that much! Savefile is less capable, and not as well tested. It does have versioning support built-in as a first class feature.

Savefile is not yet a very widely used project. However, although there may be bugs, the intention is that the quality should be enough for production.

Cargo.toml:

savefile="0.13"
savefile-derive="0.13"

Sample

extern crate savefile;
use savefile::prelude::*;

#[macro_use]
extern crate savefile_derive;


#[derive(Savefile)]
struct Player {
    name : String,
    strength : u32,
    inventory : Vec<String>,
}

fn save_player(player:&Player) {
    save_file("save.bin", 0, player).unwrap();
}

fn load_player() -> Player {
    load_file("save.bin", 0).unwrap()
}

fn main() {
	let player = Player { name: "Steve".to_string(), strength: 42,
        inventory: vec!(
            "wallet".to_string(),
            "car keys".to_string(),
            "glasses".to_string())};

    save_player(&player);

    let reloaded_player = load_player();

    assert_eq!(reloaded_player.name,"Steve".to_string());
}

Changelog

0.13 Support generic structs without Savefile type-constraints

Previously, if you tried to implement the following struct:

#[derive(Savefile)]
pub struct ExampleGeneric<T> {
    pub x: T
}

You would get compiler errors, because T cannot be serialized using Savefile. However, as a user, it may be that the struct ExampleGeneric doesn't always need to be serializable. What is really required, is that whenever an attempt is made to serialize a particular instance, then the type of that instance has to be serializable.

Other derive-macros, like the 'Debug' macro,

0.12 Support for char

It turns out that the very basic type 'char' was not actually supported by savefile.

This release fixes this oversight.

0.11.1 Support for unit structs

Savefile-derive gains support for unit structs. I.e, the following now compiles:

#[derive(Savefile)]
struct MyUnitStruct;

0.11 Improve performance of bit-vec serialization, upgrade arrayvec, support more datatypes

Savefile lacked support for u128 and i128 types. This is fixed.

Also: Slight improvements to the serialization and deserialization of bit-vec. The on-disk format has changed, but the deserializer knows how to read the old versions. Bit-vec are no longer supported on big-endian machines. Please get in touch if this is a big limitation. The reason for this change is that it allows to use a more efficient format. On a big-endian machine conversion would be needed, and this would be expensive and hard to test without access to a big-endian machine.

PRs for big-endian support would be accepted.

Also, adds support for bit-set crate and rustc-hash.

Arrayvec upgraded to version 0.7. They have changed their API slightly. See arrayvec docs.

This version updates the 'syn' and 'quote' dependencies to versions 1.0.

Savefile now supports HashSet and HashMap with custom hashers. Deserialize is only supported if the hasher implement Default (there's no way to provide a state-ful hasher to deserialized hashmaps).

0.10.1 Make dependencies even more configurable, and upgrade some dependencies

The following configurable features have been created:

  • "compression" - Enables compression and decompression (using library 'bzip2')
  • "encryption" - Enables encryption support (using library 'ring')

The following dependencies have been made configurable: "bit-vec", "arrayvec", "smallvec", "indexmap", "parking_lot"

Also, the following dependencies have been upgraded:

  • parking_lot, from 0.11 to 0.12
  • rand, from 0.7 to 0.8 (only used by 'encryption' feature)
  • bzip2, from 0.3.2 to 0.4 (only used by 'compression' feature)

0.9.1 Reduce default dependencies, and some other improvements

More ergonomic load_file-method

The load_file method's path parameter has been changed to accept anything implementing AsRef. Previously, a &str was required, which meant that the idiomatic Path and PathBuf types were not accepted.

Migration note: If you were specifying type parameters explicitly to load_file, or similar functions, you now need to add a ",_". So


    let object = load_file::<MyType>("save.bin",0);

Must become:


    let object = load_file::<MyType,_>("save.bin",0);

However, an easier option which has always worked and continues to work is:

    let object : MyType = load_file("save.bin",0);

I hope this does not cause too many problems. The reason is that having functions which open files require '&str' was never a good design, since in principle there could be files whose names are not actually valid utf8. Such files would not be possible to open using Savefile with the old design.

Make bzip2 and ring dependencies optional

Put bzip2 and ring dependencies behind feature flags. This makes it easy for users who do not wish to use compression or encryption to opt out of these dependencies.

These features are not active by default, so be sure to enable them in Cargo.toml like this, if you want to use them:

savefile = { version = "0.13", features = ["ring","bzip2"] }

Arguably, savefile should never have included this support, since it is something that can really be added easily by other crates. There is some convenience having it built-in though, hopefully making it configurable provides the best of both worlds.

Add SavefileNoIntrospect-derive

It's now possible to opt out of automatically deriving the Introspect-trait, but still automatically derive the serialization traits. It was previously possible to do the opposite, automatically deriving the introspect trait but not the serialization traits. This gap is now filled.

To derive all traits: #[derive(Savefile)]

To derive only Introspect: #[derive(SavefileIntrospectOnly)]

To derive all but Introspect: #[derive(SavefileNoIntrospect)]

0.8.3 Fix bug with savefile_introspect_ignore attribute

Specifying the savefile_introspect_ignore on a field triggered a bug if that field was not the last field of the datatype. The bug caused a mismatch in the index of the field during introspect, which would make fields not visible through introspection.

0.8.2 Update dependencies

  • parking_lot from 0.10 -> 0.11
  • smallvec 1.4 -> 1.6 (made possible by parking_lot upgrade)
  • Make Removed implement Clone, Copy, PartialEq etc. Removed fields shouldn't limit what traits a struct can implement.
  • Also make Removed implement Send and Sync. It's a zero-sized type, there are no issues with threading here.
  • Add support for std::borrow::Cow. Thanks to github user PonasKovas for this patch!

0.8.1 Stop depending on the 'failure' crate

This also means that SavefileError now (finally) implements the Error trait.

0.8.0 Support for min_const_generics

Savefile now supports serializing and deserializing arbitrarily sized arrays, even on stable rust.

Note that 0.8.0 is compatible with Rust 1.51 and later only. If you need support for older rust versions, you should stick with 0.7.x.

0.7.5 Deduplicaton of Arc

Previously, serialization of Arc was not possible. Support is now added, including deduplication of str objects. Note that the deduplication is not actually in the serialized format, just in the result in memory after deduplication. The deduplication does not know how the memory graph looked before saving, it simply makes it so that identical strings are backed by the same memory after loading.

This could cause problems if the code is somehow dependent on the addresses of &str objects. However, this should be rather rare in practice. Just file a bug if you feel that this could be a problem!

0.7.4 Add introspect for PathBuf

PathBuf did not implement Introspect, which had the effect that trying to use derive(Savefile) on anything containing a PathBuf would fail, since the derive macro requires all components to implement all the Savefile traits.

0.7.3 Support for co-existence with Serde

Savefile-derive would previously not work correctly if one tried to use it in a crate where Serde was also used.

This has been fixed.

Also, support for serializing/deserializing PathBuf.

0.8.0

(Not published as of yet)

  • Support for arbitrary size arrays, even on stable (thanks to min_const_generics now supported in rust).

Minimum supported rust version for 0.8.x is 1.51.

0.7.2 Support for stable compilers

Savefile is now usable with a stable compiler, not just nightly.

When run on stable, the following features stop working:

  • The whole 'ReprC' subsystem. This means serialization of byte arrays (or other small copy-types) is not as fast as it could be. The slow-down can be several orders of magnitude.

  • Serialization of arbitrary sized arrays. On stable, only arrays of sizes 0-4 are supported.

  • Specialisation of introspection for hashmaps with string keys. This means introspection for hashmaps is not as nice.

The nightly-only features are activated automatically when a nightly compiler is used.

Also, support for Arc<[T]> .

0.7.1 Better support for ArrayVec

The arrayvec crate has long been a dependency, but the actual ArrayVec type was not supported. We did support ArrayString, but not until 0.7.1 was ArrayVec itself supported.

0.7.0 Update some stale dependencies

The dependencies on bitvec, arrayvec and parking_lot where to old versions. They have been updated to:

bit-vec = 0.6

arrayvec = 0.5

parking_lot = 0.10

0.6.1 Fix bad reference to SavefileError

If you get compilation error saying that SavefileError is not declared, you need this small fix.

0.6.0 Critical fix to encryption-routines

This is a breaking change. Hopefully the last one! There is now a more detailed file header, which may make it possible to avoid breaking changes to the base binary framework in the future.

There were two bugs in how encrypted files were encrypted and decrypted. Data corruption could occur.

Also, savefile now supports bzip2-compression. Like the encryption-support, this is just for convenience. It should probably, earnestly, belong out of tree. But I kind of like the idea of "batteries included".

0.5.0 Introspection

Savefile now includes an introspection feature. See more in the docs.

0.4.0 Breaking Change

I just realized that 'ignore' was a very bad name for a custom attribute, since this is now a built-in attribute into the Rust language.

I have prefixed all savefile-attributes with the string "savefile_" .

This breaks existing code, in a rather silent way. The fix is simply to update all usages of savefile-attributes to include prefix 'savefile_' . The samples in the docs are correct.

0.3.0 Breaking Change

Also, version 0.3.0 breaks binary compatibility with 0.2.. This is because arrays of generic length are now supported (using Rust nightly's const_generics-feature). Previously short arrays were supported, and were (hackishly) serialized as tuples. Now arrays are truly supported, although very large arrays may cause the stack to be exhausted since the deserialization framework treats arrays as values. This means that any arrays serialized using 0.2. cannot be deserialized using 0.3.*.

Contact me if this is a showstopper. My general feeling, though, is that there are no users of this software except the author.

Docs

The savefile docs are available at: https://docs.rs/savefile/latest/savefile/

Features and goals

Features savefile has:

  • Fast binary serialization and deserialization
  • Support for old versions of the save format
  • Completely automatic implementation using "custom derive". You do not have to figure out how your data is to be saved.

Features savefile does not have:

  • Support for recursive data-structures

Features savefile does not have, and will not have:

  • Support for external protocols/data formats. There'll never be json, yaml, xml or any other backends. Savefile uses the savefile format, period.
  • Support for serializing graphs. Savefile can serialize your data if it has a tree structure in RAM, without loops.
  • Support for serializing boxed traits ("objects"). You can (probably) hack this in by manually implementing the Serialize and Deserialize traits and somehow select concrete types in the deserializer manually.

License

Savefile is licensed under either of

at your option.

MIT License text:

Copyright 2018 Anders Musikka

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Dependencies

~1–8.5MB
~159K SLoC