3 ms·
There's been a lot of work recently to enable GC-free D code. Yes, that means some of the standard library is off bounds, as are some of the built-in operators
by atilaneves 9y ago
There's been a lot of work recently to enable GC-free D code. Yes, that means some of the standard library is off bounds, as are some of the built-in operators (new, array concatenation). However, you can have _static_ guarantees that there will be no GC allocations whatsoever. Writing an executable?
`void main() @nogc { /* ... */ }`
Done.
I've written a log of `@nogc` code lately.
- gpderetta 9y agoThen what? How much of the standard library and the library ecosystem compiles with nogc? Subsetting languages (and comunities) usually doesn't end well...
- atilaneves 9y agoDepends on the kind of code you write. std.algorithm? No problem