Commit Graph

8 Commits

Author SHA1 Message Date
64c6083283
flake: add gogen ad-hoc cmd
All checks were successful
continuous-integration/drone/push Build is passing
2022-06-20 17:34:48 +02:00
faaf19b73f
flake: allow building for {x86_64,aarch64}-darwin
All checks were successful
continuous-integration/drone/push Build is passing
2022-06-20 15:58:44 +02:00
c0d8f8e6e8
go(algo): rework the plotting func, add util.go
All checks were successful
continuous-integration/drone/push Build is passing
2022-06-20 03:32:48 +02:00
86226ac76f
fix(go): RandomSearch -> RandomSearchNG
All checks were successful
continuous-integration/drone/push Build is passing
that is, a next-gen (actually working) version of the algo...
also rm the attempt at plotting before another rework.
2022-06-20 03:04:59 +02:00
5b7c0a16a4
go: add plotting capability
All checks were successful
continuous-integration/drone/push Build is passing
2022-06-18 05:27:10 +02:00
8ea9e5faf7
flake: allow GOPROXY var default for nix build
All checks were successful
continuous-integration/drone/push Build is passing
...mainly due to arbitrarily failing ci builds, as this doesn't appear
to affect local builds/nix builds on remote builders, just fresh builds
in the ci.
the explanation for why this is happening might be that certain package
VCS's don't allow many/frequent connections from IP ranges other than
GOPROXY's (Google's).
that is sheer speculation, though.
however, it is still true that there are "no" failed ci builds with
GOPROXY env var set to its default value (left untouched), which does
indeed indicate that the above mentioned might be the root cause of the
issue after all.
2022-06-25 00:28:34 +02:00
b3787da640
go: implement RandomSearch (wip)
All checks were successful
continuous-integration/drone/push Build is passing
2022-06-17 01:54:30 +02:00
43b9d611a2
initial commit 2022-06-14 16:46:11 +02:00