Metaprogramming is less fun in D

Re:Metaprogramming is less fun in D by atilaneves on Friday April 21, 2017 @12:08PM (#14166780)

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.

[ Parent | on HN ]

Re:Metaprogramming is less fun in D by gpderetta on Friday April 21, 2017 @02:34PM (#14168080)

Then what? How much of the standard library and the library ecosystem compiles with nogc?

Subsetting languages (and comunities) usually doesn't end well...

[ Parent | on HN ]

Re:Metaprogramming is less fun in D by atilaneves on Saturday April 22, 2017 @11:01AM (#14172849)

Depends on the kind of code you write. std.algorithm? No problem

[ Parent | on HN ]