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 proposal in that the main audience will probably use it in a library and not in vanilla Go. But it was still a very valid point. thanks again. On Monday, October 5, 2020 at 3:19:02 AM UTC+3 jake...@gmail.com wrote: > 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, 2020 at 4:50:10 PM UTC-4 kortschak wrote: > >> 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 misinterpreting this section in some way? >> > >> >> I'm curious as to which examples of "before the change" you think are >> invalid. From what I can see there, one is borderline (in the last >> example there is no package selector, but it could have been a dot >> import and is likely this way for brevity). The rest look like normal >> method invocations, which are the standard way for this kind of thing >> to be done in the current implementations of matrix and tensor >> operations in Go. >> >> Dan >> >> >> -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/f49975aa-5a76-45b7-a158-b1067b1dc580n%40googlegroups.com.
