You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
address review: use jemallocator feature name and mutually exclusive cfg guards
- Switch all cfg guards from feature = "tikv-jemallocator" to
feature = "jemallocator" (the public crate feature name)
- Make allocator cfg guards mutually exclusive with not() clauses
so only compile_error! fires when both features are enabled
- Clarify env vars docs that allocator-specific vars are build-dependent
- Fix Polars badge markdown line break in README.md
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: docs/ENVIRONMENT_VARIABLES.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -78,7 +78,7 @@ Several dependencies also have environment variables that influence qsv's perfor
78
78
*`POLARS_BACKTRACE_IN_ERR` - if set to 1, includes backtrace in polars-related error messages.
79
79
80
80
> ℹ️ **NOTE:** To get a list of all active qsv-relevant environment variables, run `qsv --envlist`.
81
-
Relevant env vars are defined as anything that starts with `QSV_`, `MIMALLOC_`, `JEMALLOC_`, `MALLOC_CONF` & the proxy variables listed above.
81
+
Relevant env vars always include anything that starts with `QSV_`, `MALLOC_CONF` & the proxy variables listed above. Allocator-specific env vars are build-dependent: `MIMALLOC_` vars are included when qsv is built with mimalloc support, and `JEMALLOC_` vars are included when qsv is built with jemalloc support.
0 commit comments