I have no idea if Araq has any children but I suspect he would leave any legacy
for them. I think this is how much he hates inheritance.
On my own behalf, I dont care much, selfishly, if it is methods or
vtables/interfaces as long as it will support some kind of polymorphism because
I have
@bpr
> You could implement a dynamically type OOPL in a statically typed one without
> using OO features at all in the implementation.
Definitely, obviously. I could implement Spry in plain C - if I wanted to write
C But one of the primary ideas in Spry is to try to leverage as much as
> Also, thanks @dataman, for
>
> Also bitops module (very useful) added.
Note, bitops module was provided by Mr Parashurama some months ago:
[https://github.com/nim-lang/Nim/pull/5201](https://github.com/nim-lang/Nim/pull/5201)
> The original "obviously" was referring to the fact that since Spry code is
> dynamic it leads to a lot of dynamic dispatch going on in the Spry
> interpreter - which is basically implemented using Nim methods.
You could implement a dynamically type OOPL in a statically typed one without
Ok, sorry, I mistakenly thought it was obvious that I meant that I use methods
in the Spry implementation (Spry is written in Nim). But reading what I wrote I
can understand it wasn't clear. The original "obviously" was referring to the
fact that since Spry code is dynamic it leads to a lot of
> In Spry I use methods a lot, obviously, since Spry is dynamically typed.
Do you mean, you use them whilst coding in Spry, or while coding the Spry
interpreter? Certainly in a Smalltalk like language, or in Java, you'll use
methods a lot, as there aren't other options.
> Also, I would like
In [Spry](http://sprylang.org) I use methods a lot, obviously, since Spry is
dynamically typed. I think I use multimethods only a tad, for things like plus,
minus etc to properly dispatch on combinations of integers and floats. But
nothing that you couldn't solve using a bit of conditionals or
> If you do, you may consider put some words into documentation what to do to
> achieve similar behaviour because there is quite a lot of people that are
> comfortable with that approach.
Agreed on documentation. The VTable section of the manual is short, and there's
no tutorial. IMO it would
First of all. Congratulations.
> But you're spot on, I hope this feature means we can remove method from the
> language.
If you do, you may consider put some words into documentation what to do to
achieve similar behaviour because there is quite a lot of people that are
comfortable with that
> Ahhh damn, I thought you'd go for the first option and add the feature soon
me too - normally documentation takes longer than implementation...
> Yeah sorry about that, will update the manual.
Ahhh damn, I thought you'd go for the first option and add the feature soon
I'm really happy to read that **method** is on the chopping block. If it's any
consolation, I think it was a bold and promising experiment, and even if it was
a mistake
> Added to macro which allows JSON to be unmarshalled into a type.
This is a big deal for me. I do a lot of web backend work, and this macro will
make my life so much easier. I've been playing around with Mongodb recently,
and I can see this particular macro massively simplifying my code.
>
> They're not in the compiler sources at all. This section should be removed
> from the manual, or the feature added. I was looking forward to trying this
> out, in the hope that we'll see method deprecated if there's an easy to use
> alternative for dynamic dispatch.
Yeah sorry about that,
Congratulations!
Also bitops module (very useful) added.
First, congratulations! This is a really good release, I've been waiting for
Nim concepts.
> I tried thy example from the manual but the compiler complains about
> undeclared identifier vtref
They're not in the compiler sources at all. This section should be removed from
the manual, or the
I am eager to try it!
Cool ! Awesome and nice job !!
congrats! How can I activate the VTable types described in the manual
[https://nim-lang.org/docs/manual.html#generics-vtable-types](https://nim-lang.org/docs/manual.html#generics-vtable-types)
? I tried thy example from the manual but the compiler complains about
undeclared identifier vtref.
Yay!
When can we expect docker image to be updated?
Thanks.
Congratulations, lots of fixes and sensible additions. World domination is
inevitable.
congrats!
Hooray, nimers!
> Yes, all the concepts enhancements made it into this release!
Could you (or Zahary) please give a short overview of the concept improvements
in 0.17.0?
Congratulations!
It's one of those days ...
[https://nim-lang.org/blog/2017/05/17/version-0170-released.html](https://nim-lang.org/blog/2017/05/17/version-0170-released.html)
Enjoy! (Yes, all the concepts enhancements made it into this release!)
25 matches
Mail list logo