4 ms·
I saw this the other day and really appreciated it. It was a nice change from how some other languages (WHO SHALL NOT BE NAMED) just say "no, we're not adding t
by sdegutis 11y ago
I saw this the other day and really appreciated it. It was a nice change from how some other languages (WHO SHALL NOT BE NAMED) just say "no, we're not adding this, and if you keep thinking we should then you're just not smart." This Swift document on the other hand explains thoroughly their reasoning behind it.
- _ak 11y agoThe languages that you mean probably have this information somewhere, just buried in some mailing list archive instead of compiled like this. Not that people would stop complaining even with such readily available information.
- cwzwarich 11y agoSome open source projects prefer to avoid discouraging prospective contributors, even if they know that the task the contributor is currently working on has no chance of acceptance. The hope is usually that avoiding discouragement will build a larger community, and that contributors will eventually realize the futility of their efforts or otherwise organically move towards making productive contributions to the project.
- briandear 11y agoWhat wacky logic. If I am going to spend valuable time helping a project only to let the work simply be wasted, I will organically move to some other project that values my contribution enough to not waste my time.
- nkozyra 11y agoJust to clarify, you're not talking about Go here, right? Because they make posts like this with some regularity about language design and leave the door open on a number of suggestions/changes