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
d
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 stil
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 documented
> I think fewer words with the same meaning are easier to understand.
I agree, although @OderWat's suggestion is too succinct :)
I will do my best to shorten that sentence. I'm fairly sure that Manning's
proofreaders/copyeditors will also flag up these issues to me before the book
goes to print
I think that says the same thing more succinctly ... and I think fewer words
with the same meaning are easier to understand.
