-
## Description
Program panics when serde_json is built with **arbitrary_precision** feature
```
thread 'actix-server worker 0' panicked at src\http_services\api\dashboard\summary.rs:11:14:
calle…
-
It's a little surprising to me that enabling `serde-arbitrary-precision` by itself does nothing
and requires `serde-float` to also be enabled.
Would you be open to changing this so that enabling `…
-
**Reported by rcurtin on 6 Nov 43643786 13:21 UTC**
Right now everything works on double and arma::mat. Based on #300, it would be useful to support arbitrary-precision types (within the confines of …
-
Any interest in adding support for arbitrary precision?
I imagine something like,
``` go
func (cfg Config) FormatPrecise(duration time.Duration, precision time.Duration) string
FormatPrecise(60 * t…
-
When I enable `serde_json` feature "arbitrary_precision" in my project, I get schemas that look like
```yaml
type: array
minItems:
$serde_json::private::Number: '3'
items:
$ref: '#/component…
-
### What would you like to see added to PyNWB?
I just got this question from @urut
> We're exporting things with matnwb and running through pynwb validator and it gives error below. question …
-
Is there a convenient way to introduce arbitrary precision integers (bignum) in Janet? Perhaps through long strings?
-
Currently they're limited to 32-bit since that's all JS supports. They're supposed to be bigints.
-
We Ideally need need an arbitrary-precision float type to do intermediate calculations on. This is going to be necessary in order to achieve accuracy when handling `long double`
-
Currently, we can't properly handle some large numbers that e.g. are bigger than `u64`, but the spec allows it