Chad Kunde

I have to agree with @sbinet about the usefulness of a `ZipXY(x,y []float64) XYer)` function. A portion of the users will have existing slices of structs that can easily implement...

Let's avoid re-inventing the wheel here. There's an international standard that translators are used to, which is the strings in a `messages.pot` file and translations in the respective `.po` file....

A couple thoughts: 1) Happy New Year to you both! I hope in this coming year we're able to take this tool from "experimental fork" to "extendable ecosystem." 2) Right...

@13rac1 @bwplotka - Created a quick idea as to how we can use the existing extension/option setup to add parsing/rendering options. #32

Not the one I would design if we were starting from scratch, but the goldmark ecosystem already exists using this pattern.

The internal package is more for organization and cleanliness than functionality. It's all of the assembly code for vector operations specific to numgo. Since assembly isn't very user-friendly, I thought...

I like the idea of combining the ndim meta-data. Shape, error, and the like will be the same no matter the underlying type. The use of `interface{}` types is an...

For those methods, I was using `a.data` as a canary. Since it's required to index into `a.data`, `a.shape` can be used there. We should add a tests to the creation...

This might be connected to the other problem I've been trying to solve: Slicing and views. An idea that came up in conversation was changing the structure of the Array64...

This is a good first step in getting offsets incorporated. All indexing into the data slice will need to be re-evaluated to get that built in, though. None of the...