bossmc / pinboard Goto Github PK

View Code? Open in Web Editor NEW

26.0 2.0 4.0 77 KB

A threadsafe way to publish data, just stick it on the pinboard

License: MIT License

Rust 100.00%

concurrency rust eventually-consistent

pinboard's Introduction

Pinboard

An eventually-consistent, lock-free, mutable store of shared data.

Just stick it on the pinboard!

Documentation

https://docs.rs/pinboard/

Usage

Install from crates.io by adding pinboard to your Cargo.toml:

[dependencies]
pinboard = "2.0.0"

Now you can create a Pinboard, share it between your users (be they Futures, threads or really anything else) and start sharing data!

use pinboard::NonEmptyPinboard;
use std::{thread, time::Duration};

let weather_report = NonEmptyPinboard::new("Sunny");

crossbeam::scope(|scope| {
  scope.spawn(|_| {
    thread::sleep(Duration::from_secs(10));
    weather_report.set("Raining");
  });
  scope.spawn(|_| {
    loop {
      println!("The weather is {}", weather_report.get_ref());
      thread::sleep(Duration::from_secs(1));
    }
  });
});

pinboard's People

Contributors

Stargazers

Watchers

Forkers

chriscoomber benjamingill-metaswitch pepyakin tomchaplin

pinboard's Issues

Method to create a `Pinboard` from an `Option`

Would make creating Pinboards easier in some cases

Requires `AcqRel` for `set()` and `clear()`?

I think, in set() and clear(), it's necessary to swap self.0 with the AcqRel ordering (instead of Release). Because otherwise, guard.unlinked(t) is not necessarily happening after the initialization of the data contained in t.

For example, suppose that an invocation "A" of set() writes a value t and another invocation "B" of set() is replacing t. Then B's invocation of guard.unlinked(t) should happen after A's invocation of Owned::new(t). However, with only Release ordering we cannot guarantee that.

By the way, thank you for building this wonderful library. I needed pinboard in building a new version of Crossbeam, so I reimplemented it with the name AtomicBox: https://github.com/jeehoonkang/crossbeam-epoch/blob/hazard-pointer/src/sync/atomic_box.rs (warning: no documentation at all yet!) I'll properly acknowledge the pinboard crate before submitting it as a PR to crossbeam-epoch.

Destructors are not called when replacing a pinboards contents

When storing data in a pinboard, if the contents are replaced, the old data does not have the destructors called, this leads to a memory leak.

I have attached a crate which demonstrates the issue, this can be verified by running valgrind against the example (using nightly-2017-07-06 as later versions seem to be broken).

pinboard-test.zip

bossmc / pinboard Goto Github PK

pinboard's Introduction

Pinboard

Documentation

Usage

pinboard's People

Contributors

Stargazers

Watchers

Forkers

pinboard's Issues

Method to create a `Pinboard` from an `Option`

Requires `AcqRel` for `set()` and `clear()`?

Destructors are not called when replacing a pinboards contents

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent