Why maintain a standalone GC ,instead of v8's oilpan/orinoco (also c++)

dart-lang / sdk

The Dart SDK, including the VM, JS and Wasm compilers, analysis, core libraries, and more.

https://dart.dev

BSD 3-Clause "New" or "Revised" License

10.28k stars 1.58k forks source link

Why maintain a standalone GC ,instead of v8's oilpan/orinoco (also c++) #59588

Closed gintominto5329 closed 7 hours ago

gintominto5329 commented 10 hours ago

hi , why does the dart-sdk maintain a separate private GC-ing lib. ,when gogle-v8-engine's oilpan library can be used ,because i have heard that the dart-team has not-much resources ,so why ?

also if someone knows orinoco (concurrent ,generational GC) vs. oilpan ?

thanks

dart-github-bot commented 10 hours ago

Summary: User questions why Dart uses a custom GC instead of V8's Oilpan/Orinoco, citing resource constraints. They also request a comparison of Orinoco and Oilpan.

mraleph commented 7 hours ago

Because GCs usually are closely tied to internals of a specific VM/compiler and are not easily reusable across different implementations. You can't just #include "v8/only_gc.h" and call it a day. It just does not work like that.