Bug Description

Looks like the module is initialized with the global config value once it is initialized. Future kernels that are added to the module then only use the value at initialization, and don't respect the global setting even though the compilation happens after the point where the global setting is changed.

This is especially painful for code that imports some dependencies that already initialize warp modules, before the user has any chance to even modify the setting themselves.

System Information

No response