FAQ
Hi there,

The syntastic vim plugin uses go build as an on-save hook to check the code
for syntax errors, but with the slower builds in go 1.5 it's no longer
feasible to do that in some cases as vim becomes unresponsive for too long
(while waiting for the build to finish), every time you save a file. I've
found that setting GOGC=off speeds up the build a little bit, but I'm
wondering if there are any other shortcuts one could take when using go
build merely as a syntax checker?

Cheers,
Guilherme

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Search Discussions

  • Michael Hudson-Doyle at Aug 27, 2015 at 9:57 am
    Does gofmt not work well enough as a syntax checker? I find it does for me.

    Cheers,
    mwh
    PS: Hi salgado :-)
    On 27 August 2015 at 21:46, Guilherme Salgado wrote:
    Hi there,

    The syntastic vim plugin uses go build as an on-save hook to check the code
    for syntax errors, but with the slower builds in go 1.5 it's no longer
    feasible to do that in some cases as vim becomes unresponsive for too long
    (while waiting for the build to finish), every time you save a file. I've
    found that setting GOGC=off speeds up the build a little bit, but I'm
    wondering if there are any other shortcuts one could take when using go
    build merely as a syntax checker?

    Cheers,
    Guilherme

    --
    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+unsubscribe@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+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/d/optout.
  • Guilherme Salgado at Aug 27, 2015 at 10:22 am
    Hi Michael :)

    gofmt doesn't report undefined names or missing/too-many function
    arguments, which is something I find quite helpful to have on my on-save
    hook.

    Cheers,
    On 27 August 2015 at 10:57, Michael Hudson-Doyle wrote:

    Does gofmt not work well enough as a syntax checker? I find it does for me.

    Cheers,
    mwh
    PS: Hi salgado :-)
    On 27 August 2015 at 21:46, Guilherme Salgado wrote:
    Hi there,

    The syntastic vim plugin uses go build as an on-save hook to check the code
    for syntax errors, but with the slower builds in go 1.5 it's no longer
    feasible to do that in some cases as vim becomes unresponsive for too long
    (while waiting for the build to finish), every time you save a file. I've
    found that setting GOGC=off speeds up the build a little bit, but I'm
    wondering if there are any other shortcuts one could take when using go
    build merely as a syntax checker?

    Cheers,
    Guilherme

    --
    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+unsubscribe@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+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/d/optout.
  • Andrew MacKenzie at Aug 27, 2015 at 1:49 pm
    golint?
    On Thursday, August 27, 2015 at 6:23:08 AM UTC-4, Guilherme Salgado wrote:

    Hi Michael :)

    gofmt doesn't report undefined names or missing/too-many function
    arguments, which is something I find quite helpful to have on my on-save
    hook.

    Cheers,

    On 27 August 2015 at 10:57, Michael Hudson-Doyle <michael...@canonical.com
    <javascript:>> wrote:
    Does gofmt not work well enough as a syntax checker? I find it does for
    me.

    Cheers,
    mwh
    PS: Hi salgado :-)

    On 27 August 2015 at 21:46, Guilherme Salgado <gsal...@gmail.com
    <javascript:>> wrote:
    Hi there,

    The syntastic vim plugin uses go build as an on-save hook to check the code
    for syntax errors, but with the slower builds in go 1.5 it's no longer
    feasible to do that in some cases as vim becomes unresponsive for too long
    (while waiting for the build to finish), every time you save a file. I've
    found that setting GOGC=off speeds up the build a little bit, but I'm
    wondering if there are any other shortcuts one could take when using go
    build merely as a syntax checker?

    Cheers,
    Guilherme

    --
    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...@googlegroups.com <javascript:>.
    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+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/d/optout.
  • Guilherme Salgado at Aug 27, 2015 at 3:30 pm

    On 27 August 2015 at 13:07, Andrew MacKenzie wrote:
    golint?
    It doesn't report the kind of errors I mentioned below, does it?
    On Thursday, August 27, 2015 at 6:23:08 AM UTC-4, Guilherme Salgado wrote:

    Hi Michael :)

    gofmt doesn't report undefined names or missing/too-many function arguments, which is something I find quite helpful to have on my on-save hook.

    Cheers,
    On 27 August 2015 at 10:57, Michael Hudson-Doyle wrote:

    Does gofmt not work well enough as a syntax checker? I find it does for me.

    Cheers,
    mwh
    PS: Hi salgado :-)
    On 27 August 2015 at 21:46, Guilherme Salgado wrote:
    Hi there,

    The syntastic vim plugin uses go build as an on-save hook to check the code
    for syntax errors, but with the slower builds in go 1.5 it's no longer
    feasible to do that in some cases as vim becomes unresponsive for too long
    (while waiting for the build to finish), every time you save a file. I've
    found that setting GOGC=off speeds up the build a little bit, but I'm
    wondering if there are any other shortcuts one could take when using go
    build merely as a syntax checker?

    Cheers,
    Guilherme

    --
    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...@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+unsubscribe@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+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/d/optout.
  • Minux at Aug 27, 2015 at 5:43 pm

    On Thu, Aug 27, 2015 at 5:46 AM, Guilherme Salgado wrote:

    The syntastic vim plugin uses go build as an on-save hook to check the
    code for syntax errors, but with the slower builds in go 1.5 it's no longer
    feasible to do that in some cases as vim becomes unresponsive for too long
    (while waiting for the build to finish), every time you save a file. I've
    found that setting GOGC=off speeds up the build a little bit, but I'm
    wondering if there are any other shortcuts one could take when using go
    build merely as a syntax checker?
    x/tools/cmd/gotype?

    --
    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+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/d/optout.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupgolang-nuts @
categoriesgo
postedAug 27, '15 at 9:47a
activeAug 27, '15 at 5:43p
posts6
users4
websitegolang.org

People

Translate

site design / logo © 2022 Grokbase