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
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
//! Primitive fixed-point decimal types.
//!
//! For example, `ConstScaleFpdec<i64, 4>` means using `i64` as the underlying
//! representation, and the static scale is `4`.
//!
//!
//! # Features
//!
//! - Fixed-point. The scale is bound to the *type* but not each *value*.
//!
//! - Decimal. Using integer types to represent numbers with a scaling factor
//! (also called as "scale") in base 10 to achieve the accuracy. This is a
//! [common idea](https://en.wikipedia.org/wiki/Fixed-point_arithmetic#Representation).
//!
//! - The `+` and `-` operations only perform between same types in same scale.
//! There is no implicitly type or scale conversion. This makes sense, for we
//! do not want to add `Balance` type by `Price` type.
//!
//! - The `*` and `/` operations accept operand with different types and scales,
//! and allow the result's scale specified. Certainly we need to multiply
//! between `Balance` type and `Price` type.
//!
//! - Supports 2 ways to specify the scale: *const* and *out-of-band*. See
//! the [Specify Scale](#specify-scale) section for details.
//!
//! - Supports cumulative error. See the [Cumulative Error](#cumulative-error)
//! section for details.
//!
//! - Supports both signed and unsigned types.
//!
//! - Supports scale larger than the significant digits of the underlying integer
//! type. For example `ConstScaleFpdec<i8, 4>` represents numbers in range
//! [-0.0128, 0.0127].
//!
//! - Supports negative scale. For example `ConstScaleFpdec<i8, -2>` represents
//! numbers in range [-12800, 12700] with step 100.
//!
//! - `no_std`.
//!
//!
//! # Specify Scale
//!
//! There are 2 ways to specify the scale: *const* and *out-of-band*:
//!
//! - For the *const* type [`ConstScaleFpdec`], we use Rust's *const generics*
//! to specify the scale. For example, `ConstScaleFpdec<i64, 4>` means
//! scale is 4.
//!
//! - For the *out-of-band* type [`OobScaleFpdec`], we do NOT save the
//! scale with decimal types, so it's your job to save it somewhere
//! and apply it in the following operations later. For example,
//! `OobScaleFpdec<i64>` takes no scale information.
//!
//! Generally, the *const* type is more convenient and suitable for most
//! scenarios. For example, in traditional currency exchange, you can use
//! `ConstScaleFpdec<i64, 2>` to represent balance, e.g. `1234.56` USD and
//! `8888800.00` JPY. And use `ConstScaleFpdec<u32, 6>` to represent all
//! market prices since 6-digit-scale is big enough for all currency
//! pairs, e.g. `146.4730` JPY/USD and `0.006802` USD/JPY:
//!
//! ```
//! use primitive_fixed_point_decimal::{ConstScaleFpdec, fpdec};
//! type Balance = ConstScaleFpdec<i64, 2>; // 2 is enough for all currencies
//! type Price = ConstScaleFpdec<u32, 6>; // 6 is enough for all markets
//!
//! let usd: Balance = fpdec!(1234.56);
//! let price: Price = fpdec!(146.4730);
//!
//! let jpy: Balance = usd * price;
//! assert_eq!(jpy, fpdec!(180829.71));
//! ```
//!
//! However in some scenarios, such as in cryptocurrency exchange, the
//! price differences across various markets are very significant. For
//! example `81234.0` in BTC/USDT and `0.000004658` in PEPE/USDT. Here
//! we need to select different scales for each market. So it's
//! the *Out-of-band* type:
//!
//! ```
//! use primitive_fixed_point_decimal::{OobScaleFpdec, fpdec};
//! type Balance = OobScaleFpdec<i64>; // no global scale set
//! type Price = OobScaleFpdec<u32>; // no global scale set
//!
//! // each market has its own scale configuration
//! struct Market {
//! base_asset_scale: i32,
//! quote_asset_scale: i32,
//! price_scale: i32,
//! }
//!
//! // let's take BTC/USDT market as example
//! let btc_usdt = Market {
//! base_asset_scale: 8,
//! quote_asset_scale: 6,
//! price_scale: 1,
//! };
//!
//! // we need tell the scale to `fpdec!`
//! let btc: Balance = fpdec!(0.34, btc_usdt.base_asset_scale);
//! let price: Price = fpdec!(81234.0, btc_usdt.price_scale);
//!
//! // we need tell the scale difference to `checked_mul()` method
//! let diff = btc_usdt.base_asset_scale + btc_usdt.price_scale - btc_usdt.quote_asset_scale;
//! let usdt = btc.checked_mul(price, diff).unwrap();
//! assert_eq!(usdt, fpdec!(27619.56, btc_usdt.quote_asset_scale));
//! ```
//!
//! Obviously it's verbose to use, but offers greater flexibility.
//!
//! Another example is the SQL `Decimal` data type.
//! In the server end, the scale of each decimal column is fixed on created
//! (at runtime), so it fits `OobScaleFpdec`.
//! While in the client end, the application knows the business logical and
//! the scale of each decimal column ahead (at compilation time), so it fits
//! `ConstScaleFpdec`.
//!
//!
//! # Cumulative Error
//!
//! As is well known, integer division can lead to precision loss; multiplication
//! of decimals can also create higher precision and may potentially cause
//! precision loss.
//!
//! What we are discussing here is another issue: multiple multiplication and
//! division may cause cumulative error, thereby exacerbating the issue of
//! precision loss. See [`int-div-cum-error`](https://docs.rs/int-div-cum-error)
//! for more information.
//!
//! In this crate, functions with the `cum_err` parameter provide control
//! over cumulative error based on `int-div-cum-error`.
//!
//! Take the transaction fees in an exchange as an example. An order may be
//! executed in multiple deals, with each deal independently charged a fee.
//! For instance, the funds scale is 2 decimal places, one order quantity
//! is `10.00` USD, and the fee rate is `0.003`. If the order is executed all
//! at once, the fee would be `10.00 × 0.003 = 0.03` USD. However, if the
//! order is executed in five separate deals, each worth 2.00 USD, then the
//! fee for each deal would be `2.00 × 0.003 = 0.006` USD, which rounds up
//! to `0.01` USD. Then the total fee for the 5 deals would be `0.05` USD,
//! which is significantly higher than the original `0.03` USD.
//!
//! However, this issue can be avoid if using the cum_err mechanism.
//!
//! ```
//! use primitive_fixed_point_decimal::{ConstScaleFpdec, CumErr, Rounding, fpdec};
//! type Balance = ConstScaleFpdec<i64, 2>;
//! type FeeRate = ConstScaleFpdec<i16, 6>;
//!
//! let deal: Balance = fpdec!(2.00); // 2.00 for each deal
//! let fee_rate: FeeRate = fpdec!(0.003);
//!
//! // normal case
//! let mut total_fee = Balance::ZERO;
//! for _ in 0..5 {
//! total_fee += deal.checked_mul(fee_rate).unwrap(); // 2.00*0.003=0.006 ~> 0.01
//! }
//! assert_eq!(total_fee, fpdec!(0.05)); // 0.05 is too big
//!
//! // use `cum_err`
//! let mut cum_err = CumErr::new();
//! let mut total_fee = Balance::ZERO;
//! for _ in 0..5 {
//! total_fee += deal.checked_mul_ext(fee_rate, Rounding::Round, Some(&mut cum_err)).unwrap();
//! }
//! assert_eq!(total_fee, fpdec!(0.03)); // 0.03 is right
//! ```
//!
//!
//! # Features
//!
//! - `serde` enables serde traits integration (`Serialize`/`Deserialize`).
// modules:
//
// ConstScaleFpdec OobScaleFpdec
// ^ ^
// +---------------\ /--------------+
// | | | |
// +----------+--------+ +---+-----------+---+ +-------+---------+
// | const_scale_fpdec | | none_scale_common | | oob_scale_fpdec |
// +-------------------+ +-------------------+ +-----------------+
// +---------------------------------------------------------------+
// | fpdec_inner: FpdecInner trait |
// +---------------------------------------------------------------+
// +------------------------------------+ +-----------------------+
// | inner_shorts: i8,i16,i32,i64 | | inner_i128: i128 |
// | u8,u16,u32,u64 | | u128 |
// +------------------------------------+ +-----------------------+
pub use crateConstScaleFpdec;
pub use crateFpdecInner;
pub use crate;
pub use ;
/// Error in converting from string.
use ;
use fmt;
/// Build decimal from integer or float number easily.
///
/// It accepts 1 argument for `ConstScaleFpdec`, and accepts 1 extra
/// argument for `OobScaleFpdec`, the out-of-band scale of course.
///
/// Panics:
///
/// It wraps `TryFrom` trait and will panic if `try_from()` fails.
///
/// Examples:
///
/// ```
/// use primitive_fixed_point_decimal::{ConstScaleFpdec, OobScaleFpdec, fpdec};
/// type DecConst = ConstScaleFpdec<i64, 2>;
/// type DecOob = OobScaleFpdec<i64>;
///
/// let d1: DecConst = fpdec!(1.23); // 1 argument for ConstScaleFpdec
/// let d2: DecOob = fpdec!(1.23, 2); // 2 arguments for OobScaleFpdec
/// ```
/// Used by method `checked_mul_ratio()` only.
/// For primitive integer types.