QuickJS, the Next Generation: a mighty JavaScript engine
83726bb00c
* Add utility functions, improve integer conversion functions - move `is_be()` to cutils.h - add `is_upper_ascii()` and `to_upper_ascii()` - add extensive benchmark for integer conversion variants in **tests/test_conv.c** - add `u32toa()`, `i32toa()`, `u64toa()`, `i64toa()` based on register shift variant - add `u32toa_radix()`, `u64toa_radix()`, `i64toa_radix()` based on length_loop variant - use direct converters instead of `snprintf()` - copy NaN and Infinity directly in `js_dtoa1()` - optimize `js_number_toString()` for small integers - use `JS_NewStringLen()` instead of `JS_NewString()` when possible - add more precise conversion tests in microbench.js - disable some benchmark tests for gcc (they cause ASAN failures) |
||
|---|---|---|
| .github/workflows | ||
| doc | ||
| examples | ||
| gen | ||
| test262@c1281dba45 | ||
| tests | ||
| .gitignore | ||
| .gitmodules | ||
| CMakeLists.txt | ||
| cutils.c | ||
| cutils.h | ||
| dirent_compat.h | ||
| getopt_compat.h | ||
| libbf.c | ||
| libbf.h | ||
| libregexp-opcode.h | ||
| libregexp.c | ||
| libregexp.h | ||
| libunicode-table.h | ||
| libunicode.c | ||
| libunicode.h | ||
| LICENSE | ||
| list.h | ||
| Makefile | ||
| qjs.c | ||
| qjsc.c | ||
| quickjs-atom.h | ||
| quickjs-c-atomics.h | ||
| quickjs-libc.c | ||
| quickjs-libc.h | ||
| quickjs-opcode.h | ||
| quickjs.c | ||
| quickjs.h | ||
| README.md | ||
| repl.js | ||
| run-test262.c | ||
| test262-fast.conf | ||
| test262.conf | ||
| test262_errors.txt | ||
| unicode_download.sh | ||
| unicode_gen.c | ||
| unicode_gen_def.h | ||
| v8-tweak.js | ||
| v8.js | ||
| v8.sh | ||
| v8.txt | ||
⚡️ QuickJS - A mighty JavaScript engine
Friendly QuickJS fork focused on reigniting the project.
Overview
In October 2023 @bnoordhuis and @saghul decided to fork the QuickJS project with the aim of reigniting it. They reached out to the original authors (@bellard and @chqrlie) about their intentions.
As of December 2023 the initial goal was somewhat accomplished. @bellard resumed working on the project and both parties have been pulling patches from each other since.
As of early 2024 both projects agree the proper path forward involves merging both projects and combining the efforts. While that may take a while, since both projects diverged in certain areas, there is willingness to go in this direction from both sides.