> Hint: Araq recently said that the manual on GC_ref/unref is basically wrong.
And then I changed my mind, it's correct. For the default GC. It is a bad interface. > This, ladies and gentlemen is what I would call a major clusterf_ck and it > doubtlessly results in many unnecessary problems, bugs, and trouble as well > as to people seeing that, turning around, and walking away from Nim. No, it's something that you personally seem to care about the most to the point we should stop all other development on Nim until this one issue is resolved. I'm sorry to tell you, you are not the center of the universe, people also work on what they need and what they think will help Nim succeed. > Unless, for instance, the C FFI is sufficiently (interpretation on the > generous side, please) and properly documented (e.g. -> GC_[ref|unref]()) we > have no right to truthfully assert that Nim has a good C interface. It is "sufficiently" and properly documented. Don't mix manual memory management and GC'ed memory management. As the manual says. As c2nim does it. > Simple rule: if something isn't well documented it should be regarded as > non-existing. There is nothing "simple" here, "well documented" is not an objective criterion.
