I support a smoother deprecation process, like the one Araq suggested, because
the abrupt change in #12321 creates conditions where csize has different
meaning in Nim 1.0.0 and the next release, making it difficult to maintain
backward compatibility in libraries. Also, the deprecation process
> It's Araq's toy, he can do whatever he wants.
>
> And yeah, sometimes I have the veto right but it's quite rare that I use it.
Alright, then I understand. I actually don't know how this goes in other
programming languages as I don't follow them too closely, so it may be the
norm. This
The proper solution is to deprecate `csize` and that's what we will do.
Breaking code nilly-willy wasn't required in order to fix/improve the situation
and so that's why it was reverted.
And yeah, sometimes I have the veto right but it's quite rare that I use it. I
also don't understand the
> the project leader has a veto right over community
I just want to emphasize this point. It's Araq's toy, he can do whatever he
wants. Choosing to use his Nim is our voluntary choice. If someone's not happy,
they can create a fork.
Please, can we, common and not-that-brilliant people, get a better explanation
for
[https://github.com/nim-lang/Nim/pull/12447](https://github.com/nim-lang/Nim/pull/12447)?
In my understanding, from that PR it seems that the project leader has a veto
right over community. After some
