nim-nim

Results 18 comments of nim-nim

``` diff -uNr go-moremath-033754ab1fee508c9f98f2785eec2365964e0b05.orig/fit/lsquares.go go-moremath-033754ab1fee508c9f98f2785eec2365964e0b05/fit/lsquares.go --- go-moremath-033754ab1fee508c9f98f2785eec2365964e0b05.orig/fit/lsquares.go 2017-02-10 20:34:28.000000000 +0100 +++ go-moremath-033754ab1fee508c9f98f2785eec2365964e0b05/fit/lsquares.go 2018-03-20 13:07:28.200088026 +0100 @@ -9,7 +9,7 @@ "math" "strings" - "github.com/gonum/matrix/mat64" + "gonum.org/v1/gonum/mat" ) // LinearLeastSquares computes the...

I'm trying to generate module files from expanded go source archives, with a little more control of what ends up in the module files, than the go tooling currently does....

Basically, I would need something to write info files from RevInfo? and something else to parse (simplified?) RevInfos from module.Version

And the tidy functions in the same package would also be real useful

I need the bit that defines the content of an info file structure https://tip.golang.org/cmd/go/#hdr-Module_proxy_protocol states > The JSON-formatted metadata about a given module corresponds to this Go data structure, which...

> I thought I had found the definition in `src/cmd/go/internal/modcmd` but I'm not finding it anymore It's probably intended to be a subset of RevInfo in /src/cmd/go/internal/modfetch/codehost/codehost.go Don't really see...

Thanks for caring! Go is currently living its own mid-life crisis: it has made easy to write a lot of code, so now there is this huge pile of code...

@egonelbre Thanks for taking the time to think about it. Your misunderstanding stems from the fact you think in isolated package terms. Individual packages are utterly uninteresting for integrators. Integrators...

Detecting cycle-free module boundaries is just the first step, I agree. If the limits are too exotic or complex that strongly hints the codebase needs restructuring (and code analysis tools...

So Unicase is not exposed with the 'unic' tag in Cormorant? Ok that’s good to know. I was, indeed, mistaken. Generally for my deployment target I try to avoid compatibility...