On Friday, 15 July 2022 at 09:27:51 UTC, LinguisticMystic wrote:

It is perfectly usable without a GC

You have access to malloc/free from libc and also allocators, so you can do what ever you want!

I am working on an online RPG targeting WASM without touching the GC at all, no RAII (thanks to scope guards aka defer, scope(exit)), no exceptions and it's been super smooth

• game server

• login server

• master server

• front end

• database stuff

D is a very pragmatic language, i still use the GC for tooling projects and the deployment scripts where the GC doesn't have any impact at all, it was very useful to have even thought not necessary

https://www.kdom.xyz/

If you don't want the GC then you know what you are doing you don't want to deal with 3rd-party anyways since they can mess up your memory allocation strategy

You can consume C/C++ code with D, so you can consume their entire ecosystem with ease

I consume GLFW on desktop, Freetype for fonts, OpenGL/OpenAL for gpu/audio and PostgreSQL for the database, they are all C projects and the integration is super smooth

And there are lot of people around developing D libraries that are @nogc compatible

On Friday, 15 July 2022 at 11:48:31 UTC, Araq wrote:

That's false

I work with D and also some C libraries, and i can debug my program and step into C code without issues

Proof: (lib: mongoose, statically linked)

https://i.imgur.com/C2vjGOo.png

Little Rant:

Guys, when someone comes and ask if something is feasible without component X, you shouldn't tell them they are wrong for wanting to do it the way they want to do it

D is perfectly great for using without the GC, just like using C is perfectly great without a GC, just like Rust is perfectly great withotu a GC, they are equivalent

GC is only here as an optional scratch buffer, and it is very handy to have when you need it

We should welcome people with their usecase and make them feel safe for wanting to achieve what they want to achieve

If someone asks to not use the GC and you tell them "you shouldn't really", they'll go check the next language in their list of "interesting languages"

D a great language because it is pragmatic and polyvalent, it is a strength, as a community, let's be pragmatic too and accept that some folks doesn't want to use a GC!

It's like OOP, not everything needs it, not every meal needs salt, not every mattress needs to be white, not every cars needs to be grey

On Friday, 15 July 2022 at 15:05:24 UTC, ryuukk_ wrote:

I think he was referring to mixing a compiled language with Lua, or something like that.

On Friday, 15 July 2022 at 09:27:51 UTC, LinguisticMystic wrote:

Learn like the GC doesn't exist. You won't even try hard to learn. Most things are things you already know and are familiar with. I think, you won't say also "what's up with that GC".

Welcome to the club, to the D family...😀
SDB@79

On Friday, 15 July 2022 at 14:55:45 UTC, ryuukk_ wrote:

Same here, products are @nogc but to do them you need quite a lot of tools and one-time experiments, and those can be with GC usage.

On Friday, 15 July 2022 at 14:55:45 UTC, ryuukk_ wrote:

Not template heavy C++.

On Saturday, 16 July 2022 at 07:04:03 UTC, Ola Fosheim Grøstad wrote:

Taking a chance to advertise, up to c++17 mostly not a problem, some tweaks by hand might be needed in generated code though.

https://github.com/Superbelko/ohmygentool

On Friday, 15 July 2022 at 09:27:51 UTC, LinguisticMystic wrote:

The @nogc is primarily that you aren't allocating or handling anything that uses (or may cause) the GC to run. You might need @nothrow as well.

Personally i love putting as much temporary allocations as i can on the stack, and leaving cleanup to instantly and cleanly be handled by the function cleanup code.

In C/D one of my favorite things would be to allocate everything as a single block and then assign pointers as necessary so a single free will handle it rather than say 20-30.

But if you aren't using the built-in array allocation, or an algorithm that will try to change the allocated memory then it should be fine. Not sure about the allocator template use, but doing structs and malloc/free should be a workable pair without relying on the GC at all.

But i'm very rusty on all this anymore :(