@Libman Thanks for the clarification
@dom96 I though that 0.18 is coming first.
Anyway, I hope to see you guys in FOSDEM in Brussels, and by then I probably
can share some thought, meantime, I'm trying to use Nim on daily basis and get
to understand it better. it's amazing how fast I can comple
@dom96, Very interesting! Any hints that you may provide on the timeline for
the 1.0 release? I know that there are a lot of people who are waiting until
1.0 hits before seriously looking at Nim and so this is quite a big deal. If it
is coming very soon then that could be quite interesting. Is t
Thanks, interesting alias syntax!
Also, there's some nice syntax for aliasing over in the issue tracker over here:
[https://github.com/nim-lang/Nim/issues/7090](https://github.com/nim-lang/Nim/issues/7090)
Edit: Have also requested that this be added to the Nim Cookbook:
[https://github.com/btb
> This thread scares me as a new Nim user
This brainstorming session is long expired.
* * *
Summarizing Araq's verdict with quotes from above:
{
* "Skins were part of my original Nim 'vision'."
* "I now think syntax skins should be an editor feature, not a compiler
feature, so relax."
Honestly, I'm not for or against skins one way or another - I see the value and
the potential pitfalls as described by various folks. What is more interesting
from this thread is the potential ability of Nim to allow developing such skins
in so called user-space. If I could write a completely al
Thanks. I was confusing the `T: typedesc` notation with Scala's context bounds
since they share the same syntax.
