thepudds

@thepudds1

Tweets tend to be about Go, Go Modules, and fuzzing.

Vrijeme pridruživanja: kolovoz 2018.

Tweetovi

Blokirali ste korisnika/cu @thepudds1

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @thepudds1

  1. proslijedio/la je Tweet
    31. sij

    Ok, finally tagged gopls/v0.3.0! VS Code should auto-update even if you installed the pre-release. There are so many great changes in this one! Check out the release notes here:

    Prikaži ovu nit
    Poništi
  2. proslijedio/la je Tweet

    Open source is the foundation on which my career was built, and few have contributed more to my success than . From the day memcached prevented my app's imminent demise, to my first Golang contribution, Brad has set the bar for what it means to be a project maintainer.

    Poništi
  3. proslijedio/la je Tweet
    9. sij

    "How to write Go code" has been entirely re-written, and now also covers Go modules!

    Poništi
  4. 19. pro 2019.

    Nice new post on Modules by , focusing on version selection. Also, don’t forget the option of `go get -u all` for latest versions of all your direct and indirect dependencies. Go’s MVS is about a more stable *starting* point, but you can be more aggressive

    Poništi
  5. proslijedio/la je Tweet

    , if you are not fuzz testing your code, why? (Please, please, please retweet for reach)

    Poništi
  6. proslijedio/la je Tweet
    8. stu 2019.
    Odgovor korisnicima i sljedećem broju korisnika:

    The v2 directory satisfies the import compatibility rule and works for GOPATH based dependency management tools. If you don't need to support GOPATH based tools, you can use git branches and tags and no major version directory -- everything in the root directory.

    Poništi
  7. proslijedio/la je Tweet

    1) Found a very used package that has custom parsing logic 2) Copy-pasted a fuzzer from go-fuzz-corpus for a similar format 3) Found 2 unique crashes in the first 24 seconds of go-fuzz needs first-class citizenship for fuzzing

    Poništi
  8. 12. lis 2019.

    Great intro blog post on modules just published by . Focuses on the “why”, so that the mechanics make more sense. Worth a read!

    Poništi
  9. proslijedio/la je Tweet
    27. ruj 2019.

    “Publishing Go Modules” by posted on the Go Blog. Learn how to version and publish modules! 📦

    Poništi
  10. proslijedio/la je Tweet

    Turned a corner over the past two days with modules. As my understanding of the problem space gets better, the tooling, messages and mechanics are starting to make more sense. I am starting to gain some focus on opportunities for usability improvements.

    Poništi
  11. proslijedio/la je Tweet
    3. ruj 2019.
    Poništi
  12. 3. ruj 2019.

    More details on these and other changes in the 1.13 release notes. Don't be the last one of your friends to read them! ;-) 5/5

    Prikaži ovu nit
    Poništi
  13. 3. ruj 2019.

    If you get an `invalid pseudo-version` error with modules, see the 1.13 release notes for why, as well as likely resolution. 4/5

    Prikaži ovu nit
    Poništi
  14. 3. ruj 2019.

    If you have private code, you'll likely want to configure the GOPRIVATE setting (such as `go env -w GOPRIVATE=*.corp.com`) or you can use the more fine-grained variants GONOPROXY or GONOSUMDB, though most people might prefer the simpler GOPRIVATE. 3/5

    Prikaži ovu nit
    Poništi
  15. 3. ruj 2019.

    Downloading dependencies is also often 5x - 10x faster in 1.13 due to visiting fewer dependencies, and due to defaulting to a GOPROXY (which is more efficient than using VCS as a coarse-grained transport). 2/5

    Prikaži ovu nit
    Poništi
  16. 3. ruj 2019.

    In 1.13, `go get` arguments have better behavior, including `go get -u ./...` from your module root upgrades the direct and indirect dependencies of your module, exclusive of test dependencies. `go get -u -t ./...` is similar, but also upgrades test dependencies. 2/5

    Prikaži ovu nit
    Poništi
  17. 3. ruj 2019.

    If you use modules, it is well worth your time to review the Go 1.13 Release Notes: 1/5

    Prikaži ovu nit
    Poništi
  18. proslijedio/la je Tweet
    29. kol 2019.

    this can be the last RC before official go1.13. try it and report bugs, celebrate improvements, and tweet surprises! many new things lined up to make our long weekend more interesting.

    Poništi
  19. proslijedio/la je Tweet
    17. kol 2019.

    Now that this is generating results, I really hope the Go community will contribute more fuzz functions for Go 1.14. And polish what’s there.

    Poništi
  20. proslijedio/la je Tweet
    17. kol 2019.
    Poništi

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·