Rushmore Mushambi

@nshalman That hack is not necessary at all. For example, you can do something like the following instead:- ``` sh export GOPATH=$(mktemp -d /tmp/cerana.XXXXXX) mkdir -p $GOPATH/src/github.com/cerana cd $GOPATH/src/github.com/cerana git...

@sheenobu This is a bug in the current version (v1.1.1). @kamilchm I meant to report this earlier but I never got around to doing it. For now I just use...

> Current Go vendoring scheme implies that every dependency found in vendor makes the same dependency in GOPATH obsolete and go2nix doesn't need to add it as an external dependency...

@kamilchm > cat glide.lock | grep -o "name:.*" | awk '{ pkg = $2; gsub(/\//, "-"); printf("mkdir -p $GOPATH/src/%s && rsync -aP ~/.glide/cache/src/https-%s/ $GOPATH/src/%s/\n", pkg, $2, pkg); }' | xargs...

It's an internal company project that's not available publicly. If I remove the last part to get the input being piped to `xargs` I get:- ``` mkdir -p $GOPATH/src/github.com/gin-gonic/gin &&...

> I follow dep and there's a good news golang/dep#500 - one more step to unify go dependency management. Awesome.

See https://github.com/surrealdb/surrealdb/issues/74 for more information on how `NULL` and `NONE` work in SurrealDB. I proposed dropping `NULL` in that issue because I prefer `NONE`'s behaviour, considering how they are implemented.

Hi @tobiemh, yes `NULL`s are definitely an interesting topic to say the least. For the purpose of just getting the job done I think either approach is fine. However, I...

Thanks for the explanation @tobiemh! Seeing NULL mentioned in some places and NONE in others was confusing me. I thought perhaps you had started off using NONE but now want...

> We also need to deal with null values from JSON when working with JavaScript libraries. I can see how this can be a problem for fields or tables with...