Mirror of forum.nim-lang.org

3347 :: Unifiing resource management like destructors and finalizers

• Veladus (orginal) [2017-11-18T15:11:00+01:00] view original

  Couldn't render post #21080.

---

• Araq (orginal) [2017-11-18T21:03:47+01:00] view original

  • Destructors and move semantics are still in development and scheduled for Nim version 2. There have been previous attempts to implement them and they were "hacked together".
  • The way to write a destructor is

  proc `=destroy`(x: var T)
  Run

  The other syntaxes will be removed.

  • There is no direct distinction between stack and heap for destruction, it's just that the existing Nim uses a GC and finalizers to clean things up or try-finally/defer, just like Java, C#, Python, Ruby, Go, JavaScript etc. In fact, like every other language that is not C++.

---

• Veladus (orginal) [2017-11-18T22:29:49+01:00] view original

  Okay, so in Nim v2 we will have a resource management system with a syntax which is valid for heap and stack variables? The roadmap just suggests they should interact. btw. I wasn't concerned about the implementation, since this has to be diffrent, of course.

  @Araq I looked all your examples up and none of them have two diffrent syntaxes for stack and heap deallocation. In most of them the use of a destructor/finalizer is highly discouraged, will this be the case for Nim too?

---

• Araq (orginal) [2017-11-19T12:56:58+01:00] view original

  I don't understand your questions. The default GC is pretty aggressive and so finalizers end up being called "early enough" so we don't really discourage them.

---