#undo #redo

no-std redo

Provides undo-redo functionality with static dispatch and manual command merging

68 releases (34 breaking)

✓ Uses Rust 2018 edition

0.38.0 Nov 1, 2019
0.37.0 Sep 30, 2019
0.35.0 Jul 2, 2019
0.32.1 Mar 25, 2019
0.2.1 Feb 15, 2017

#57 in Data structures

Download history 39/week @ 2019-07-19 34/week @ 2019-07-26 60/week @ 2019-08-02 98/week @ 2019-08-09 1/week @ 2019-08-16 1232/week @ 2019-08-23 81/week @ 2019-08-30 213/week @ 2019-09-06 76/week @ 2019-09-13 664/week @ 2019-09-20 89/week @ 2019-09-27 79/week @ 2019-10-04 16/week @ 2019-10-11 144/week @ 2019-10-18 72/week @ 2019-10-25

941 downloads per month


2.5K SLoC


Travis Crates.io Docs

Provides undo-redo functionality with static dispatch and manual command merging.

It is an implementation of the command pattern, where all modifications are done by creating objects of commands that applies the modifications. All commands knows how to undo the changes it applies, and by using the provided data structures it is easy to apply, undo, and redo changes made to a receiver. Both linear and non-linear undo-redo functionality is provided through the Record and History data structures. This library provides more or less the same functionality as the undo library but is more focused on performance instead of ease of use.


  • Command provides the base functionality for all commands.
  • Record provides linear undo-redo functionality.
  • History provides non-linear undo-redo functionality that allows you to jump between different branches.
  • Queue wraps a Record or History and extends them with queue functionality.
  • Checkpoint wraps a Record or History and extends them with checkpoint functionality.
  • Configurable display formatting is provided when the display feature is enabled.
  • Time stamps and time travel is provided when the chrono feature is enabled.
  • Serialization and deserialization is provided when the serde feature is enabled.


  • Commands can be merged into a single command by implementing the merge method on the command. This allows smaller commands to be used to build more complex operations, or smaller incremental changes to be merged into larger changes that can be undone and redone in a single step.
  • The receiver can be marked as being saved to disk and the data-structures can track the saved state and tell the user when it changes.
  • The amount of changes being tracked can be configured by the user so only the n most recent changes are stored.


Add this to Cargo.toml:

redo = "0.38"

And this to main.rs:

use redo::{Command, Record};

struct Add(char);

impl Command<String> for Add {
    type Error = &'static str;

    fn apply(&mut self, s: &mut String) -> Result<(), Self::Error> {

    fn undo(&mut self, s: &mut String) -> Result<(), Self::Error> {
        self.0 = s.pop().ok_or("`s` is empty")?;

fn main() -> Result<(), &'static str> {
    let mut record = Record::default();
    assert_eq!(record.as_receiver(), "abc");
    assert_eq!(record.as_receiver(), "");
    assert_eq!(record.as_receiver(), "abc");


Licensed under either of

at your option.


Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.