Valentin Churavy

I am not sure what should happen here `SharedArray` only works when all processes are on the same machine. Something that is not guaranteed with SLURM.

As I said it is not something that SharedArray can really support, but maybe it could throw an error.

A while back I came up with the following example for where currently the GC fails us. I didn't write it with early finalization in mind and it was more...

This is pretty much the simplest thing. The only complexity here is the allocation tracking so that you can immediatly tell if you are successful. You can remove the tracker......

IIRC it's a linear scan over the finalizer list, to remove the object from it. So maybe create a couple thousand object with a finalizer and benchmark it then.

Cleanup is normally performed when a process shuts down on the Compute node, so you are right we could and should do a better job with error handling here.

Don't we build pthreads for out mingw cross compiler? On Wed, Nov 16, 2022, 10:14 Tim Besard ***@***.***> wrote: > The DLL generated here also doesn't contain a single pthread_...

``` It will likely re-compile almost everything (sad) because so many packages now directly or indirectly depend on SnoopPrecompile, but we don't yet see a way around that while also...

Either `@precompile_setup` or `@precompile_all_calls` would insert a: ``` parse(Bool, SnoopPrecompile.Preference.@load_preference("snoop_precompile", "true")) ``` Which would then allow the user to set a preference flag per Package.

> Or are you saying that each package would have a LocalPreferences.toml that sets snoop_precompile just for that package? Yes. IIUC the issue is that changing the preference causes the...