Re: Learning Nim

[twetzel59]

Awesome, thanks! I'll take precaution with unstable features, but otherwise 
that's encouraging 

Re: Learning Nim

[dom96]

> > if I write a library today, will it be completely obsolete or compile a 
> > year or two for now?
> 
> In my opinion, yes, based on other stuff programmed in nim that has not 
> received updates in a year. But it might happen that in a year nim reaches v1.

I disagree. Here is some proof: a library I've written a LONG time ago, 
compiles perfectly: 
[https://github.com/dom96/nim-jsonrpc](https://github.com/dom96/nim-jsonrpc). 
Sure it's not large but it proves something. Despite Nim being pre-v1 we do 
make an effort not to break things.

And v1 is indeed around the corner.

* * *

As for the features you've mentioned, I personally don't use either of them. 
Feel free to use them but beware that they may be more buggy than the rest of 
the language.

Re: Learning Nim

[Arrrrrrrrr]

> if I write a library today, will it be completely obsolete or compile a year 
> or two for now?

In my opinion, yes, based on other stuff programmed in nim that has not 
received updates in a year. But it might happen that in a year nim reaches v1.

> Should I use the new "this" argument insertion?

I think Araq wants to make it the default.

> Should I use "concepts"?

Yes. You will find bugs, but that's the only way to progress. In the past they 
used to be more limited and bugged, but recently got an overhaul.