Re: [go-nuts] internal compilation error while compiling gccgo from source solaris 10

[Amandeep Gautam]

Hi Ian,
   I compiled GMP, MPFR and MPC from source. Next, I configured gcc with 
modified options:

$srcdir/configure \
--prefix=$prefix \
--enable-languages=go \
--with-as=/opt/csw/gnu/as --with-gnu-as \
--with-ld=/usr/ccs/bin/ld --without-gnu-ld \
--with-gmp-include=/usr/gnu/gmp/include --with-gmp-lib=/usr/gnu/gmp/lib 
\
--with-mpfr=/usr/gnu/mpfr --with-mpfr-include=/usr/gnu/mpfr/include 
--with-mpfr-lib=/usr/gnu/mpfr/lib \
--with-mpc=/usr/gnu/mpc \
--with-isl=/opt/csw --with-isl-include=/opt/csw/include 
--with-isl-lib=/opt/csw/lib \
--with-build-time-tools=/opt/csw/gnu \
--enable-multilib \
--enable-shared \
--enable-static \
--disable-nls \
--disable-libquadmath \
--disable-libssp \
--disable-lto \
--disable-libgomp

The make step is still failing but, to my surprise, I found that it is 
still able to find libmpfr.so.4 from the /opt/csw directory. I am guessing 
that I am not configuring something correctly. Can you please look.

Output from GBD:

-bash-3.2$ gdb /export/home/amandeep/gccgo-obj/./gcc/go1
GNU gdb (GDB) 7.7
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 

This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "sparc-sun-solaris2.10".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /export/home/amandeep/gccgo-obj/./gcc/go1...done.
(gdb) run /export/home/amandeep/gccgo-src/libgo/go/fmt/doc.go 
/export/home/amandeep/gccgo-src/libgo/go/fmt/format.go 
/export/home/amandeep/gccgo-src/libgo/go/fmt/print.go 
/export/home/amandeep/gccgo-src/libgo/go/fmt/scan.go -quiet -dumpbase 
doc.go -mcpu=v9 -auxbase-strip .libs/fmt.o -g -O2 -version -fgo-pkgpath=fmt 
-fPIC -I . -L/export/home/amandeep/gccgo-obj/./gcc -o /var/tmp//ccBuuCrV.
Starting program: /export/home/amandeep/gccgo-obj/gcc/go1 
/export/home/amandeep/gccgo-src/libgo/go/fmt/doc.go 
/export/home/amandeep/gccgo-src/libgo/go/fmt/format.go 
/export/home/amandeep/gccgo-src/libgo/go/fmt/print.go 
/export/home/amandeep/gccgo-src/libgo/go/fmt/scan.go -quiet -dumpbase 
doc.go -mcpu=v9 -auxbase-strip .libs/fmt.o -g -O2 -version -fgo-pkgpath=fmt 
-fPIC -I . -L/export/home/amandeep/gccgo-obj/./gcc -o /var/tmp//ccBuuCrV.
[Thread debugging using libthread_db enabled]
[New Thread 1 (LWP 1)]
GNU Go (GCC) version 8.2.1 20180814 (sparc-sun-solaris2.10)
compiled by GNU C version 8.2.1 20180814, GMP version 6.1.2, MPFR 
version 4.0.1-p13, MPC version 1.1.0, isl version csw-0.18-GMP

warning: MPFR header version 4.0.1-p13 differs from library version 4.0.0.
warning: MPC header version 1.1.0 differs from library version 1.0.2.
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
GNU Go (GCC) version 8.2.1 20180814 (sparc-sun-solaris2.10)
compiled by GNU C version 8.2.1 20180814, GMP version 6.1.2, MPFR 
version 4.0.1-p13, MPC version 1.1.0, isl version csw-0.18-GMP

warning: MPFR header version 4.0.1-p13 differs from library version 4.0.0.
warning: MPC header version 1.1.0 differs from library version 1.0.2.
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
/export/home/amandeep/gccgo-src/libgo/go/fmt/format.go:8:9: error: import 
file 'strconv' not found
  "strconv"
 ^
/export/home/amandeep/gccgo-src/libgo/go/fmt/format.go:9:14: error: import 
file 'unicode/utf8' not found
  "unicode/utf8"
  ^
*... and many more like this before terminating...*

/export/home/amandeep/gccgo-src/libgo/go/fmt/scan.go:688:52: error: 
expected integer, floating, complex, or string type
   s.errorString("unsigned integer overflow on token " + tok)
^

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1 (LWP 1)]
0xfbb8df24 in mpfr_init2 () from */opt/csw/lib/sparcv8/libmpfr.so.4*
(gdb) bt
#0  0xfbb8df24 in mpfr_init2 () from /opt/csw/lib/sparcv8/libmpfr.so.4
#1  0xff1d8bac in mpc_init2 () from /usr/lib/libmpc.so.3
#2  0x001c5500 in Numeric_constant::check_complex_type (this=0xffbff208, 
type=0x10944c8, issue_error=, location=...)
at 
/export/home/amandeep/gccgo-src/gcc/go/gofrontend/expressions.cc:16745
#3  0x001c588c in Numeric_constant::set_type (this=0xffbff208, 
type=0x11f4f78, issue_error=, loc=...) at 
/export/home/amandeep/gccgo-src/gcc/go/gofrontend/types.h:751
#4  0x001c5944 in Integer_expression::do_check_types (this=0x11f50e0) at 
/export/home/amandeep/gccgo-src/gcc/go/gofrontend/expressions.h:535
#5  0x001e7d04 in 

Re: [go-nuts] Re: IDE/tools that support the new Go module feature in 1.11?

[Sameer Ajmani]

+Ian C, Alan, Rebecca, Michael On the Go team are working with tool owners
to migrate tools to the new go/packages API, which adds module support and
compatibility with older workspaces.

On Sat, Aug 25, 2018 at 6:22 AM Diego Bernardes 
wrote:

> gometalinter and gotests are breaking for me. They were installed from
> vscode-go.
>
>
> Em sábado, 25 de agosto de 2018 09:45:11 UTC+1, nvcnvn escreveu:
>>
>> Hi all,
>> Do you know any IDE already support intellisense for a project using
>> "pure" Go module (without /vendor, $GOPATH)
>>
> --
> You received this message because you are subscribed to the Google Groups
> "golang-nuts" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to golang-nuts+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[go-nuts] IDE/tools that support the new Go module feature in 1.11?

[nvcnvn]

Hi all,
Do you know any IDE already support intellisense for a project using "pure" 
Go module (without /vendor, $GOPATH)

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [go-nuts] IDE/tools that support the new Go module feature in 1.11?

[Aldrin Leal]

Goland has been supporting it for a while:

https://blog.jetbrains.com/go/2018/05/18/vgo-integration-support/

--
-- Aldrin Leal,  / https://ingenieux.io/about/

On Sat, Aug 25, 2018 at 3:45 AM, nvcnvn  wrote:

> Hi all,
> Do you know any IDE already support intellisense for a project using
> "pure" Go module (without /vendor, $GOPATH)
>
> --
> You received this message because you are subscribed to the Google Groups
> "golang-nuts" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to golang-nuts+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[go-nuts] Re: IDE/tools that support the new Go module feature in 1.11?

[Diego Bernardes]

gometalinter and gotests are breaking for me. They were installed from 
vscode-go.

Em sábado, 25 de agosto de 2018 09:45:11 UTC+1, nvcnvn escreveu:
>
> Hi all,
> Do you know any IDE already support intellisense for a project using 
> "pure" Go module (without /vendor, $GOPATH)
>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[go-nuts] Problems with cache

[Peter Kleiweg]

Since Go 1.10, the cache causes many headaches. You can disable the cache 
with GOCACHE=off. Unless you work on mega projects, you don't need a cache 
anyway. But disabling the cache won't be an option in Go 1.12. What to do 
then? Stick with old version of Go?

The release notes for Go 1.11 have this to say:

" Go 1.11 will be the last release to support setting the environment 
variable GOCACHE=off to disable the build cache, introduced in Go 1.10. 
Starting in Go 1.12, the build cache will be required, as a step toward 
eliminating $GOPATH/pkg. The module and package loading support described 
above already require that the build cache be enabled. If you have disabled 
the build cache to avoid problems you encountered, please file an issue to 
let us know about them. "

However, when you file an issue, they tell you "it is working as intended". 





-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[go-nuts] What's the status of the new Go brand?

[haskell_mustard via golang-nuts]

The announcement in April said:

What’s happening next
>
 

> The website will be getting a refresh based on the new design. Since we 
> are making significant changes, we are also taking this opportunity to 
> update our website infrastructure to better serve our global community with 
> internationalization and multilingual support. The migration will happen in 
> stages over the next few months starting with this blog.


https://blog.golang.org/go-brand

A few months have passed, yet nothing has changed.

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [go-nuts] Problems with cache

[Jakob Borg]

On 25 Aug 2018, at 15:21, Peter Kleiweg 
mailto:pklei...@xs4all.nl>> wrote:

disabling the cache won't be an option in Go 1.12. What to do then?

You don’t say what your issues with the build cache are. If you did, you might 
get suggestions.

//jb

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [go-nuts] Problems with cache

[Peter Kleiweg]

Op zaterdag 25 augustus 2018 16:40:55 UTC+2 schreef Jakob Borg:
>
> On 25 Aug 2018, at 15:21, Peter Kleiweg > 
> wrote:
>
>
> disabling the cache won't be an option in Go 1.12. What to do then?
>
>
> You don’t say what your issues with the build cache are. If you did, you 
> might get suggestions.
>

Actually, setting GOCACHE=off doesn't solve all problems. So I am now back 
to Go version 1.9.7

Some problems:

 - You can't use packages that require local adjustments to the environment 
to install.
 - Code completion in Emacs doesn't work (using gocode)
 - Running Go in a Jupyter Notebook (using lgo) is slow with Go version 
1.10 and higher.

 

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [go-nuts] Problems with cache

[Ian Lance Taylor]

On Sat, Aug 25, 2018 at 7:58 AM, Peter Kleiweg  wrote:
> Op zaterdag 25 augustus 2018 16:40:55 UTC+2 schreef Jakob Borg:
>>
>> On 25 Aug 2018, at 15:21, Peter Kleiweg  wrote:
>>
>>
>> disabling the cache won't be an option in Go 1.12. What to do then?
>>
>>
>> You don’t say what your issues with the build cache are. If you did, you
>> might get suggestions.
>
>
> Actually, setting GOCACHE=off doesn't solve all problems. So I am now back
> to Go version 1.9.7
>
> Some problems:
>
>  - You can't use packages that require local adjustments to the environment
> to install.

Can you expand on this.  I'm not sure what you mean.


>  - Code completion in Emacs doesn't work (using gocode)

That sounds like a bug to be fixed.  The golang.org/x/go/packages
package is intended to use the build cache for input where
appropriate.  The likely path forward will be to make gocode use
go/packages.


>  - Running Go in a Jupyter Notebook (using lgo) is slow with Go version 1.10
> and higher.

I don't know what lgo is.  In general the cache does not slow down the
build.  Quite the opposite: in my experience, it speeds it up.  If you
see cases where the cache makes things slower, please report them so
that they can be fixed.

Ian

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [go-nuts] Problems with cache

[Sebastien Binet]

On Sat, Aug 25, 2018 at 6:54 PM Ian Lance Taylor  wrote:

> On Sat, Aug 25, 2018 at 7:58 AM, Peter Kleiweg  wrote:
> > Op zaterdag 25 augustus 2018 16:40:55 UTC+2 schreef Jakob Borg:
> >>
> >> On 25 Aug 2018, at 15:21, Peter Kleiweg  wrote:
> >>
> >>
> >> disabling the cache won't be an option in Go 1.12. What to do then?
> >>
> >>
> >> You don’t say what your issues with the build cache are. If you did, you
> >> might get suggestions.
> >
> >
> > Actually, setting GOCACHE=off doesn't solve all problems. So I am now
> back
> > to Go version 1.9.7
> >
> > Some problems:
> >
> >  - You can't use packages that require local adjustments to the
> environment
> > to install.
>
> Can you expand on this.  I'm not sure what you mean.
>
>
> >  - Code completion in Emacs doesn't work (using gocode)
>
> That sounds like a bug to be fixed.  The golang.org/x/go/packages
> package is intended to use the build cache for input where
> appropriate.  The likely path forward will be to make gocode use
> go/packages.
>

in my experience, nsf/gocode was quite problematic to properly handle Go
version bumps (I would end-up with "PANIC" messages in vim-go, resulting
from a weird mix of a new Go compiler, gocode using parts of the old one,
and my local code that would use the new one.)
I migrated to mdempsky/gocode. never looked back.


>
> >  - Running Go in a Jupyter Notebook (using lgo) is slow with Go version
> 1.10
> > and higher.
>
> I don't know what lgo is.  In general the cache does not slow down the
> build.  Quite the opposite: in my experience, it speeds it up.  If you
> see cases where the cache makes things slower, please report them so
> that they can be fixed.
>

Ian: that's https://github.com/yunabe/lgo

Peter: you could try the one from gopherdata:
https://github.com/gopherdata/gophernotes

-s

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [go-nuts] internal compilation error while compiling gccgo from source solaris 10

[Ian Lance Taylor]

On Fri, Aug 24, 2018 at 11:48 PM, Amandeep Gautam
 wrote:
> Hi Ian,
>I compiled GMP, MPFR and MPC from source. Next, I configured gcc with
> modified options:
>
> $srcdir/configure \
> --prefix=$prefix \
> --enable-languages=go \
> --with-as=/opt/csw/gnu/as --with-gnu-as \
> --with-ld=/usr/ccs/bin/ld --without-gnu-ld \
> --with-gmp-include=/usr/gnu/gmp/include --with-gmp-lib=/usr/gnu/gmp/lib
> \
> --with-mpfr=/usr/gnu/mpfr --with-mpfr-include=/usr/gnu/mpfr/include
> --with-mpfr-lib=/usr/gnu/mpfr/lib \
> --with-mpc=/usr/gnu/mpc \
> --with-isl=/opt/csw --with-isl-include=/opt/csw/include
> --with-isl-lib=/opt/csw/lib \
> --with-build-time-tools=/opt/csw/gnu \
> --enable-multilib \
> --enable-shared \
> --enable-static \
> --disable-nls \
> --disable-libquadmath \
> --disable-libssp \
> --disable-lto \
> --disable-libgomp
>
> The make step is still failing but, to my surprise, I found that it is still
> able to find libmpfr.so.4 from the /opt/csw directory. I am guessing that I
> am not configuring something correctly. Can you please look.

Maybe you need to set LD_LIBRARY_PATH to point to your newly built libmpfr?

Another approach is to copy the mpfr sources into your GCC directory,
named exactly mpfr.  Then the GCC build will automatically use that
one.

Ian




> Output from GBD:
>
> -bash-3.2$ gdb /export/home/amandeep/gccgo-obj/./gcc/go1
> GNU gdb (GDB) 7.7
> Copyright (C) 2014 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> 
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "sparc-sun-solaris2.10".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> .
> Find the GDB manual and other documentation resources online at:
> .
> For help, type "help".
> Type "apropos word" to search for commands related to "word"...
> Reading symbols from /export/home/amandeep/gccgo-obj/./gcc/go1...done.
> (gdb) run /export/home/amandeep/gccgo-src/libgo/go/fmt/doc.go
> /export/home/amandeep/gccgo-src/libgo/go/fmt/format.go
> /export/home/amandeep/gccgo-src/libgo/go/fmt/print.go
> /export/home/amandeep/gccgo-src/libgo/go/fmt/scan.go -quiet -dumpbase doc.go
> -mcpu=v9 -auxbase-strip .libs/fmt.o -g -O2 -version -fgo-pkgpath=fmt -fPIC
> -I . -L/export/home/amandeep/gccgo-obj/./gcc -o /var/tmp//ccBuuCrV.
> Starting program: /export/home/amandeep/gccgo-obj/gcc/go1
> /export/home/amandeep/gccgo-src/libgo/go/fmt/doc.go
> /export/home/amandeep/gccgo-src/libgo/go/fmt/format.go
> /export/home/amandeep/gccgo-src/libgo/go/fmt/print.go
> /export/home/amandeep/gccgo-src/libgo/go/fmt/scan.go -quiet -dumpbase doc.go
> -mcpu=v9 -auxbase-strip .libs/fmt.o -g -O2 -version -fgo-pkgpath=fmt -fPIC
> -I . -L/export/home/amandeep/gccgo-obj/./gcc -o /var/tmp//ccBuuCrV.
> [Thread debugging using libthread_db enabled]
> [New Thread 1 (LWP 1)]
> GNU Go (GCC) version 8.2.1 20180814 (sparc-sun-solaris2.10)
> compiled by GNU C version 8.2.1 20180814, GMP version 6.1.2, MPFR
> version 4.0.1-p13, MPC version 1.1.0, isl version csw-0.18-GMP
>
> warning: MPFR header version 4.0.1-p13 differs from library version 4.0.0.
> warning: MPC header version 1.1.0 differs from library version 1.0.2.
> GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
> GNU Go (GCC) version 8.2.1 20180814 (sparc-sun-solaris2.10)
> compiled by GNU C version 8.2.1 20180814, GMP version 6.1.2, MPFR
> version 4.0.1-p13, MPC version 1.1.0, isl version csw-0.18-GMP
>
> warning: MPFR header version 4.0.1-p13 differs from library version 4.0.0.
> warning: MPC header version 1.1.0 differs from library version 1.0.2.
> GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
> /export/home/amandeep/gccgo-src/libgo/go/fmt/format.go:8:9: error: import
> file 'strconv' not found
>   "strconv"
>  ^
> /export/home/amandeep/gccgo-src/libgo/go/fmt/format.go:9:14: error: import
> file 'unicode/utf8' not found
>   "unicode/utf8"
>   ^
> ... and many more like this before terminating...
>
> /export/home/amandeep/gccgo-src/libgo/go/fmt/scan.go:688:52: error: expected
> integer, floating, complex, or string type
>s.errorString("unsigned integer overflow on token " + tok)
> ^
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 1 (LWP 1)]
> 0xfbb8df24 in mpfr_init2 () from /opt/csw/lib/sparcv8/libmpfr.so.4
> (gdb) bt
> #0  0xfbb8df24 in mpfr_init2 () from /opt/csw/lib/sparcv8/libmpfr.so.4
> #1  0xff1d8bac in mpc_init2 () from /usr/lib/libmpc.so.3
> #2  0x001c5500 in Numeric_constant::check_complex_type (this=0xffbff208,
> 

Re: [go-nuts] IDE/tools that support the new Go module feature in 1.11?

[Alex Rice]

On Saturday, August 25, 2018 at 3:45:13 AM UTC-6, Aldrin Leal wrote:
>
> Goland has been supporting it for a while:
>
> https://blog.jetbrains.com/go/2018/05/18/vgo-integration-support/
>
>
> Isn't "vgo"  the older (pre- go 1.11) variant? 

I was just trying out GoLand with Go 1.11 and ran into some trouble getting 
it to use "go mod" files, even though support is mentioned in the release 
notes:

https://blog.jetbrains.com/go/2018/08/24/goland-2018-2-2-is-here/

Curious if anyone else is having success.

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [go-nuts] IDE/tools that support the new Go module feature in 1.11?

[Alex Rice]

On Saturday, August 25, 2018 at 2:19:30 PM UTC-6, Alex Rice wrote:
 

> https://blog.jetbrains.com/go/2018/08/24/goland-2018-2-2-is-here/
>
> Curious if anyone else is having success.
>
>
Oh, I see- in GoLand the New Project dialog has 3 choices: Go, Go Module 
(vgo), or Dep.

I was trying to use an existing Project.

 

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [go-nuts] Problems with cache

[Peter Kleiweg]

Op zaterdag 25 augustus 2018 19:06:27 UTC+2 schreef Sebastien Binet:
>
>
>
> On Sat, Aug 25, 2018 at 6:54 PM Ian Lance Taylor  > wrote:
>
>> On Sat, Aug 25, 2018 at 7:58 AM, Peter Kleiweg > > wrote:
>> > Op zaterdag 25 augustus 2018 16:40:55 UTC+2 schreef Jakob Borg:
>> >>
>> >> On 25 Aug 2018, at 15:21, Peter Kleiweg  wrote:
>> >>
>> >>
>> >> disabling the cache won't be an option in Go 1.12. What to do then?
>> >>
>> >>
>> >> You don’t say what your issues with the build cache are. If you did, 
>> you
>> >> might get suggestions.
>> >
>> >
>> > Actually, setting GOCACHE=off doesn't solve all problems. So I am now 
>> back
>> > to Go version 1.9.7
>> >
>> > Some problems:
>> >
>> >  - You can't use packages that require local adjustments to the 
>> environment
>> > to install.
>>
>> Can you expand on this.  I'm not sure what you mean.
>>
>>
>> >  - Code completion in Emacs doesn't work (using gocode)
>>
>> That sounds like a bug to be fixed.  The golang.org/x/go/packages
>> package is intended to use the build cache for input where
>> appropriate.  The likely path forward will be to make gocode use
>> go/packages.
>>
>
> in my experience, nsf/gocode was quite problematic to properly handle Go 
> version bumps (I would end-up with "PANIC" messages in vim-go, resulting 
> from a weird mix of a new Go compiler, gocode using parts of the old one, 
> and my local code that would use the new one.)
> I migrated to mdempsky/gocode. never looked back.
>

I tried this. It works for me too.
 

>
>
>>
>> >  - Running Go in a Jupyter Notebook (using lgo) is slow with Go version 
>> 1.10
>> > and higher.
>>
>> I don't know what lgo is.  In general the cache does not slow down the
>> build.  Quite the opposite: in my experience, it speeds it up.  If you
>> see cases where the cache makes things slower, please report them so
>> that they can be fixed.
>>
>
> Ian: that's https://github.com/yunabe/lgo
>
> Peter: you could try the one from gopherdata:  
> https://github.com/gopherdata/gophernotes
>

Yes,  it works, but is it as good as lgo? I don't know if this comparison 
is up to date:

https://github.com/yunabe/lgo#gophernotes

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [go-nuts] Problems with cache

[Peter Kleiweg]

Op zaterdag 25 augustus 2018 18:54:32 UTC+2 schreef Ian Lance Taylor:
>
> On Sat, Aug 25, 2018 at 7:58 AM, Peter Kleiweg  > wrote: 
> > Op zaterdag 25 augustus 2018 16:40:55 UTC+2 schreef Jakob Borg: 
> >> 
> >> On 25 Aug 2018, at 15:21, Peter Kleiweg  wrote: 
> >> 
> >> 
> >> disabling the cache won't be an option in Go 1.12. What to do then? 
> >> 
> >> 
> >> You don’t say what your issues with the build cache are. If you did, 
> you 
> >> might get suggestions. 
> > 
> > 
> > Actually, setting GOCACHE=off doesn't solve all problems. So I am now 
> back 
> > to Go version 1.9.7 
> > 
> > Some problems: 
> > 
> >  - You can't use packages that require local adjustments to the 
> environment 
> > to install. 
>
> Can you expand on this.  I'm not sure what you mean. 
>
>
See this issue: https://github.com/golang/go/issues/27027

 

> >  - Code completion in Emacs doesn't work (using gocode) 
>
> That sounds like a bug to be fixed.  The golang.org/x/go/packages 
> package is intended to use the build cache for input where 
> appropriate.  The likely path forward will be to make gocode use 
> go/packages. 
>
>
> >  - Running Go in a Jupyter Notebook (using lgo) is slow with Go version 
> 1.10 
> > and higher. 
>
> I don't know what lgo is.  In general the cache does not slow down the 
> build.  Quite the opposite: in my experience, it speeds it up.  If you 
> see cases where the cache makes things slower, please report them so 
> that they can be fixed. 
>

It says here: https://github.com/yunabe/lgo#go110

" lgo works with go1.10. But the overhead of code execution is 4-5x larger 
in go1.10 than go1.9. It is due to a regression of the cache mechnism of go 
install in go1.10. I recommend you to use lgo with go1.9 until the bug is 
fixed in go1.10. "

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [go-nuts] Problems with cache

[Ian Lance Taylor]

On Sat, Aug 25, 2018 at 5:16 PM, Peter Kleiweg  wrote:
> Op zaterdag 25 augustus 2018 18:54:32 UTC+2 schreef Ian Lance Taylor:
>>
>> On Sat, Aug 25, 2018 at 7:58 AM, Peter Kleiweg  wrote:
>> > Op zaterdag 25 augustus 2018 16:40:55 UTC+2 schreef Jakob Borg:
>> >>
>> >> On 25 Aug 2018, at 15:21, Peter Kleiweg  wrote:
>> >>
>> >>
>> >> disabling the cache won't be an option in Go 1.12. What to do then?
>> >>
>> >>
>> >> You don’t say what your issues with the build cache are. If you did,
>> >> you
>> >> might get suggestions.
>> >
>> >
>> > Actually, setting GOCACHE=off doesn't solve all problems. So I am now
>> > back
>> > to Go version 1.9.7
>> >
>> > Some problems:
>> >
>> >  - You can't use packages that require local adjustments to the
>> > environment
>> > to install.
>>
>> Can you expand on this.  I'm not sure what you mean.
>>
>
> See this issue: https://github.com/golang/go/issues/27027

Thanks, but disabling the cache won't fix that issue.  The issue there
is that the go tool has gotten more precise about when packages are up
to date, and will try to rebuild them if they are not up to date.
There is already a way to handle this: //go:binary-only-package.

Ian

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[go-nuts] Re: What's the status of the new Go brand?

[Steve Roth]

Hmm, I wouldn't say "nothing" has changed.  The golang.org site has gotten 
noticeably slower, particularly the package documentation.  I have no idea 
whether that's related to this migration but it's definitely unfortunate.

Steve


On Saturday, August 25, 2018 at 8:30:17 AM UTC-7, Carla Pfaff wrote:
>
> The announcement in April said:
>
> What’s happening next
>>
>  
>
>> The website will be getting a refresh based on the new design. Since we 
>> are making significant changes, we are also taking this opportunity to 
>> update our website infrastructure to better serve our global community with 
>> internationalization and multilingual support. The migration will happen in 
>> stages over the next few months starting with this blog.
>
>
> https://blog.golang.org/go-brand
>
> A few months have passed, yet nothing has changed.
>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[go-nuts] Working with import "google.golang.org/api/admin/directory/v1"

[John More]

I am using the "google.golang.org/api/admin/directory/v1" to access a G 
Suite account and everything seems to work EXCEPT:
The import defines a User structure that includes the following element 
among many others
Suspended bool  `json:"suspended,omitempty"` 

When set to false the json.Marshal treats this as an empty field which will 
not allow me to reactivate a user. 
Calling the API directly without using the library is not an option as I am 
using a service account which means I have to use a JWT and I really have 
no idea how to get the Bearer token.
Copying the user struct from the library generates a lot of compiler 
dependency errors

If anyone has run into this before.. workarounds or clues are appreciated

Thanks

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.