1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
// Copyright (c) 2021 Sebastien Braun
//
// This Source Code Form is subject to the terms of the Mozilla Public
// License, v. 2.0. If a copy of the MPL was not distributed with this
// file, You can obtain one at http://mozilla.org/MPL/2.0/.
//! [](https://crates.io/crates/eso)
//! [](https://docs.rs/eso)
//! [](https://github.com/braunse/eso/issues)
//! [](https://github.com/braunse/eso/pulls)
//! [](https://github.com/braunse/eso/commits)
//! 
//! 
//!
//! Type-level machinery for building [`Cow`](std::borrow::Cow)-like
//! types while avoiding unnecessary copies of `'static' or
//! other shareable references.
//!
//! The main feature of this crate is the [`Eso`] type, which tracks
//! whether the contained value is ephemeral (i.e. borrowed with any
//! lifetime), static/shared (i.e. can be held on to indefinitely) or
//! owned (i.e. can be moved and may be mutably accessed).
//!
//! In addition, it also statically tracks which of these is *possible*
//! at any given point in the code by encoding the information on a
//! type level using the definitions in the [`maybe`] module.
//!
//! While [`Eso`] is perfectly happy working with normal Rust references,
//! it also provides an abstraction to support a more generalized notion
//! of reference. The definitions in the [`borrow`] module describe
//! the different operations that are required to use generalized
//! references.
//!
//! ## Feature flags
//!
//! ### `allow-unsafe`: Allow usage of `unsafe` Rust
//!
//! This feature is active by default.
//!
//! `Eso` contains two usages of `unsafe`, which make the [`No`](crate::maybe::No)
//! type implement [`Send`] and [`Sync`] irrespective of its type
//! parameter.
//! This should be safe since no value of the [`No`] type can ever exist
//! and it therefore cannot participate in any races or memory safety violations.
//!
//! Nonetheless, if you want to disallow usage of `unsafe`,
//! turn off the default features in your `Cargo.toml`:
//!
//! ```toml
//! [dependencies.eso]
//! version = "0.0.2"
//! default-features = false
//! ```
pub use crateEso;
pub use crate;