Everybody has an opinion on what features Nim needs. What we need is people who
can either (A) implement those features themselves, or (B) pay someone to do
it. ;)
> Some things, owing to their prevalence, in my opinion have to be part of
> standard library of language. For example, the string methodsfunctions
> toCharArray, getBytes, reverse are in many languages.
The problem is, when is enough... I can think of a dozen things i like to see
in Nim. But
> you can also put all of the helpers you coded into a package and publish it
> with Nimble
Some things, owing to their prevalence, in my opinion have to be part of
standard library of language. For example, the string methods\functions
**toCharArray**, **getBytes**, **reverse** are in many
@Araq I am sorry I stepped on your foot. Keep on with your work on this great
language, and thank you for very good community support. I mean it without any
sarcasm.
And you are completely right, Nim needs to focus on the things that are truly
important, and don't loose focus in the details.
Garry_galler you can also put all of the helpers you coded into a package and
publish it with Nimble.
Nim is not Scala but it is very flexible and you can expand it with packages
that don't require the core to change or everyone to adopt your perspective.
Hi,
Let me add my view on this topic. I created many topics here (for example
[this](http://forum.nim-lang.org///forum.nim-lang.org/t/1333) and
[this](http://forum.nim-lang.org///forum.nim-lang.org/t/1665)) to improve the
functions in sequtils. The reception was very positive, and after some
The stdlib is mostly as generic as the lack of a working `concept`
implementation allows for. No surprises here and thanks for the update, I lived
under a rock the last ten years and don't know about C++'s iterators and D's
slices and Clojure's transfinite enumerations.
Having said that, I
Yes I really do like scala, and I think scala has a lot in the functional
programming domain, that I would like to have in Nim, too.
Here is a pattern from scala that I like to use to avoid the creation of
intermediate variables in object scope, when in practice only the result is
interesting.
Partly preamble. A week ago, I began to learn **Scala** \- so how about **Nim**
(and it's disappointing) read almost nothing (in my native language -
especially). Written for **Nim** module nimfp, implements very similar
functional paradigm that is in the **Scala** \- and this is well
