-
const object = {id: 123n}
stringify can be stored as
{"id": 123n}
Can be correctly converted to bigint instead of number during parse
-
Hi all and thank you for this great tool.
Does nswag have a feature to generate a "`bigint`" typescript var in the client proxies if the source property type in c# is "`long`"?
I would assume it…
mbfis updated
3 months ago
-
Would be useful if this lib gracefully handled native `bigint` values.
Could simply `toString()` them
-
BigInts are useful to represent 64-bit values and also for some algorithms where 53-bit precision is not enough. There's a stage 3 proposal, implemented by e.g. NodeJS, here: https://github.com/tc39/p…
-
The current version of the number cell only supports normal `Numbers` but not `BigInt` numbers (> 2^53). Two potential solutions would be to:
1. Enable the native number-cell to handle `BigInt` val…
-
Hello, I am having problems with BigInt used in action parameters.
For example:
``
if I check the parameters in action(`event.params`), I get:
`{ id: 676280779033907800, text: 'test text' }`
so i…
-
not sure how feasible this feature-request is. sqlite3 docs say INTEGERS can be 1, 2, 3, 4, 6, or 8 bytes.
is it possible to:
1. input - allow 64-bit bigint as a `param` input? e.g.
```js
db.…
-
**🧐 Motivation**
This issue is brought to my attention by a question from @wly99.
Say I want to calculate the future value of principal on a 30-year home loan:
```solidity
futurePrincipal = pr…
-
local function _get_byte8(data, i)
local a, b, c, d, e, f, g, h = strbyte(data, i, i + 7)
```
-- XXX workaround for the lack of 64-bit support in bitop:
local lo = bor(a, lshift(b, 8), lshift(c, …
-
**Why this feature is better to be included in comment-json? Please describe the scenario**
I like this library, Can you please support for bigInt number
**Provide 1-2 code examples that the usage…