A transpiler that will implement index operator methods will be very
appealing at first. But it won't be long before general operator
overloading will be added to its feature set and the result is splitting Go
to a different language...
The question is, what is best to the go community in the l
Dnia 2020-10-06, o godz. 00:56:38
Raanan Hadar napisał(a):
> To a gonum user, this proposal is about a 20% improvement and nothing to run
> home about.
> To a matlab/python programmer, this solves about 80% of their problems and
> combining this
> with the other benefits of Go is enough to stro
Lets start with saying that I think this is a valid criticism.
Although it does not solve things 100%, it does solve the heart of the
problem for me at least:
There is a mixture of index operators with functional operators in the
syntax:
The [] operator gives the reader the 'where' context an
i think this looks nice but realistically only cleans up v simple cases. a
lot of the very-verbose-and-not-so-elegant-looking multidimensional math
stuff looks "worse" than other languages because go doesn't have operator
overloading. it is not clear to me this improves syntax too much in
practic
It actually didn't change that much, I just applied your valuable feedback.
Thanks alot!
Its critical to communicate clearly.
so I changed the before and after part of the proposal to be more
approachable to people who
are less familiar with numerical libraries in Go.
Its not a trivial proposa
The examples I was looking at are gone now. That section has been
completely rewritten. So its kind of moot. Its possible that I was
confusing the 'before' and 'after' examples, since they were not clearly
labeled. In any case the rewritten version seems to make sense now.
On Sunday, October 4
On Sun, 2020-10-04 at 09:06 -0700, jake...@gmail.com wrote:
> I stopped reading at the " Show example code before and after the
> change " because many of the examples of "before the change" code
> seem to be invalid in go, and the others do not do what you seem to
> imply they do. Am I misinterpr
So I may have jumped too far ahead in that section in order to keep the
proposal short.
The examples are typical of gonum and gorgonia/tensor. I have also
implemented in my experience report a small library
in that spirit to make sure that everything worked as well.
So you are right, its not
I stopped reading at the " Show example code before and after the change "
because many of the examples of "before the change" code seem to be invalid
in go, and the others do not do what you seem to imply they do. Am I
misinterpreting this section in some way?
On Sunday, October 4, 2020 at 1
