It appears there is some issue with continue statements in notebook defined functions. In the notebook below, when I call optimalEta the function enters and goes into the loops correctly, but then the continue statement seems to bring it back to the function call site, where that continues an infinite number of times.
In optimal eta
calling obj
In obj, s = 0.0001
In obj, s = 5e-323
In obj, s = 5e-323
In obj, s = 5e-323
In obj, s = 5e-323
In obj, s = 5e-323
In obj, s = 5e-323
In obj, s = 5e-323
(and this printing does not halt).
brendan:~$ go version
go version devel +a12c1f26e4 Tue Jun 26 20:00:51 2018 +0000 darwin/amd64
brendan:~$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/brendan/Library/Caches/go-build"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/brendan/Documents/mygo"
GOPROXY=""
GORACE=""
GOROOT="/Users/brendan/gover/go"
GOTMPDIR=""
GOTOOLDIR="/Users/brendan/gover/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/l6/mhj4qjrj4437b_lgfz9pm1rw0000gn/T/go-build730485233=/tmp/go-build -gno-record-gcc-switches -fno-common"
VGOMODROOT=""
The go version is the 1.11beta (which I'm using because of #122 ).
It appears there is some issue with
continue
statements in notebook defined functions. In the notebook below, when I calloptimalEta
the function enters and goes into the loops correctly, but then the continue statement seems to bring it back to the function call site, where that continues an infinite number of times.Here is the notebook
When I run the code, I see the following output
(and this printing does not halt).
The go version is the 1.11beta (which I'm using because of #122 ).