See here: https://github.com/nim-lang/RFCs/issues/503
There is one more RFC in the works dealing with the eternal question of our time: What is an exception?
Brilliant! IC plus useable nimsuggest would be such a huge step forward.
I applaud removing async and spawn from the stdlib, that's a bold move for a 'batteries-included' language but it's a credit to the language that such a thing is possible, and to the ecosystem that we have several robust and mature replacements.
I am glad to see 'special operators' on the list; a working callOperator could enable C++ style lambdas (as a library!) that have rather moved ahead of Nim in functionality in the last few years.
I applaud removing async and spawn from the stdlib, that's a bold move for a 'batteries-included' language but it's a credit to the language that such a thing is possible, and to the ecosystem that we have several robust and mature replacements.
I'm glad the selectors.nim would remain though. I just don't think any libraries will have nearly the platform/os test coverage that Nim itself has.
It would be cool if all the libs separated from the std lib were gathered in a sort of framework so that they could be installed together, with a common docs website. Something like boost in c++
To reduce the amount of work of the Nim core team, another team can be constituted by some motivated members of the community, to manage that super library....
there shouldn't be prags
Yeah right, let's just remove pragmas 😒
Really dude, what the heck? Why would you say something like that?
Looking at the roadmap, I wanted to know if integrating CPS into the core language as a low level construct is still being considered?
Not anytime soon. Maybe for Nim v3.0.