fast_float icon indicating copy to clipboard operation
fast_float copied to clipboard

Fast and exact implementation of the C++ from_chars functions for number types: 4x to 10x faster than strtod, part of GCC 12 and WebKit/Safari

Results 39 fast_float issues
Sort by recently updated
recently updated
newest added

Perhaps fast string conversion also can be added.

This function could be simplified a bit: https://github.com/lemire/fast_float/blob/7eae925b51fd0f570ccd5c880c12e3e27a23b86f/include/fast_float/ascii_number.h#L27 replace its implementation with: `return ((val & 0xF0F0F0F0F0F0F0F0u) & (val + 0x0606060606060606u)) == 0x3030303030303030u;`

This is useful for projects that integrate FastFloat via `add_subdirectory`. In many cases the vendored FastFloat is not part of the public API and should not be exposed as such.

Updates the `actions/checkout` action used in the GitHub Actions workflow to its newest version. Changes in [actions/checkout](https://github.com/actions/checkout): > ## v3.0.2 > - [Add input `set-safe-directory`](https://github.com/actions/checkout/pull/770) > > ## v3.0.1 >...

Are there any plans to add support for hexadecimal strings? While not as common as the decimal representation, I have a few use cases related to parsing languages which have...

I'm writing a library for some scientific data management, and I have a need to parse strings of the sort `"+12.345e-02(13)"`**, which contains the value `0.12345` and the error `0.00013`....

The following blog post could be useful if we ever want to parsing `uint8_t` values: https://lemire.me/blog/2023/11/28/parsing-8-bit-integers-quickly/

As a follow up to  #216 . It's not branchless, but, nevertheless, allow to extract part of the logic so it can be reused. Running the benchmark shows no difference...

`18446744073709551615e-65` rounds to `0`, and it is the largest possible value with exponent `-65`. Therefore, we can assume the minimal exponent for which we don't round to zero actually is...

The library is already correct on these cases, but we should be explicit. Contributed by @deadalnix ``` 1/ Where float stop rounding to 0. 0.7006492321624085354e-45 0.7006492321624085355e-45 2/ Where float start...