Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

On the GC vs noGC divide #34

Open
MarvinHannott opened this issue Jan 30, 2024 · 0 comments
Open

On the GC vs noGC divide #34

MarvinHannott opened this issue Jan 30, 2024 · 0 comments

Comments

@MarvinHannott
Copy link

I think this divide is completely avoidable if data structures just accept an allocator argument. That would also make it much easier to mix strategies. Sure, that might mean that builtin dynamic arrays and hashmaps have to go because they don't have a destructor. But to be honest, thanks to operator overloading, library solutions are just as ergonomic. In practice you don't feel any difference. And maybe it would be a good thing to have fewer primitives builtin.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant