Objects casting and custom destructor about nim HOT 3 CLOSED

That's just how it works, no bug here.

from nim.

The issue is not with the basic concept of how destructors work or type conversions, but rather with how the compiler handles the implicit creation of destructors when casting between related types. The fact that an implicit destructor interferes with an explicit destructor definition without a clear message suggests there might be room for improvement in how this is handled.

Even if this behavior is technically correct according to the current Nim specification, it can lead to confusion for developers, especially when dealing with complex inheritance structures. If this is intended behavior, clarifying it in the documentation could help prevent misunderstandings in the future. If it’s not intended, then addressing it could improve the developer experience.

I’m not claiming that it’s definitively a bug, but I believe it warrants further discussion to see if this behavior could be made more intuitive or better communicated.

from nim.

There is no need to discuss it, in Nim v3 this restriction will be gone.

from nim.