There's things I'd like to contribute to the language, but some are some serious undertaking. What's the best way to know what features are more likely to be merged without having to spend weeks implementing something that could potentially just be rejected?
The best you can do is propose the feature or enhancement and allow some time for discussions and points of view to mature. Then we have an "status:accepted" label that we use to signal that if you tackle this as it's been discussed, we'll merge it.
Ah, ok. That makes sense. So make an issue with a proposed feature, wait for it to be accepted, then tackle a PR. I think this would be a great flow for everyone to follow. Thanks!
In the CS fields I am interested in programming languages, UX, Visualizations & AI. I've spent more than 10 years teaching CS.I love to social dance to swing & blues music.
If it's a reported bug/enhancement, I would say to first discuss in the issue how it could be solved.
It might seems like an extra work other than coding, but is a way to avoid doing all the coding work that might not be merged.
We do value the efforts off everybody but sometimes is more that just writing code what is needed. Making decisions sometimes requires other kind of mindset, attention and time.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
There's things I'd like to contribute to the language, but some are some serious undertaking. What's the best way to know what features are more likely to be merged without having to spend weeks implementing something that could potentially just be rejected?
The best you can do is propose the feature or enhancement and allow some time for discussions and points of view to mature. Then we have an "status:accepted" label that we use to signal that if you tackle this as it's been discussed, we'll merge it.
Ah, ok. That makes sense. So make an issue with a proposed feature, wait for it to be accepted, then tackle a PR. I think this would be a great flow for everyone to follow. Thanks!
I think we should document this flow in official Crystal wiki :)
If it's a reported bug/enhancement, I would say to first discuss in the issue how it could be solved.
It might seems like an extra work other than coding, but is a way to avoid doing all the coding work that might not be merged.
We do value the efforts off everybody but sometimes is more that just writing code what is needed. Making decisions sometimes requires other kind of mindset, attention and time.