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
Rayon has long had some logging functionality, but not well advertised.
The only mention is in the (private) module docs:
> To use in a debug build, set the env var `RAYON_LOG` as
> described below. In a release build, logs are compiled out by
> default unless Rayon is built with `--cfg rayon_rs_log` (try
> `RUSTFLAGS="--cfg rayon_rs_log"`).
>
> Note that logs are an internally debugging tool and their format
> is considered unstable, as are the details of how to enable them.
I, for one, have not "internally" used this for debugging at all, yet it
comes at some cost to all users, even disabled in release builds. At the
very least it requires `crossbeam-channel` that we're not using anywhere
else except tests. Besides that, this code also bloats the compiled size
of `rayon-core` by about 30%, and similar for its compile time.
**So let's just rip out the logger!**
The remaining uses of `crossbeam-channel` in test cases are easily
avoidable too, since `std::sync::mpsc::Sender` is now `Sync`.
(cherry picked from commit 191ade2)
0 commit comments