UserAB1236872

Yeah, I think if we solve #61 json will take care of itself.

It's largely in assembly, so it's not quite that simple. On Fri, May 8, 2015 at 12:45 PM, Olivier Gagnon [email protected] wrote: > Couldnt we just download all the files...

Granted, we could possibly do a find+replace on the assembly instructions too, but we'd have to do a lot of testing to ensure we didn't bork something. On Fri, May...

If you (or someone) submits a PR, I'd be happy to accept it. It should be a relatively straightforward patch to the generator code to sub your library for native...

This is a bit tricky, not in execution but in design. Unfortunately, since Go doesn't have optional arguments or overloading, we can't make a version of each method where you...

I'll definitely add either a buildtag or an extra make command that does everything without the SIMD stuff. I'm not sure which would be more convenient. On Thu, Sep 18,...

Other note: apparently SIMD for a Mat3 determinant is also not worth it, though this is because of the necessary passthrough to another function (you can't define assembly on a...

Let me see if I can dig it up On Wed, Oct 21, 2015 at 1:56 PM Olivier Gagnon [email protected] wrote: > @Jragonmiris https://github.com/Jragonmiris can you post your SIMD code...

Ugh, I didn't know that I have to tag each minor version individually. Still, you're missing a ton of package development if you stick with 1.2.1, including bug fixes that...

On review, perhaps we could refactor Mat/VecMN out of the core packages. If we switch to RMO in order to comply with the Go f32 package, we should probably get...