There are already a couple gc libraries in rust. I wouldnt say Go is strictly "pluggable gc" since...well you can't get rid of the gc. You can try and keep it from doing meaningful work but thats quite different than "RAII managed memory with a fallback to a gc library that targets my particular use-case"

Fully agree with you that GC should be abstracted away and used for where it shines: cycles and graphs!

is there any pluggable GC libary in rust that is both correct and stable?

The only one I've heard of is Boehm GC. Is it not correct or stable? I do not have any experience or special knowledge of it myself.

Boehm is conservative, unfortunately.

There was some consideration for a formal library based rust GC back in 2018 such that one could write GC<CyclicDataType> and get the benefits of a GC such as

- Not leaking memory - Not invoking unsafe - Not angering the rust compiler

None of those efforts stabilized to my knowledge, and the libraries developed for this task all have experimental/research tags associated to them.

For better or worse all the guides for using rust strongly encourage avoidance of primitive cyclic structures such as doubly linked lists, graphs, and other structures in favor of statically allocated fixed size variants. Like golang's preference for map/list as the only primitive structures, this is a constraint that one can get used to for most problems. But it doesn't feel great that as a language there are basic algorithms and datastructures that can't be idiomatically coded in the language.

There’s a new GC library released the other day https://blog.typingtheory.com/shredder-garbage-collection-as...

Still extremely new, of course, but has promise!

You can already use reference counting when needed. Pretty close to what you are envisioning.