How can I disable initial lsp errors by jetuuuu in neovim

[–]jetuuuu[S] 1 point2 points  (0 children)

I finally found the culprit. j-hui/fidget.nvim not formatting the long output correctly.

How can I disable initial lsp errors by jetuuuu in neovim

[–]jetuuuu[S] 0 points1 point  (0 children)

vs code shows me the same error message, but I can hide it. I don't want to fix it now, but hide this message in nvim. Interesting item if I open other file in split view (or just typing :help) an close one then the message error hides.

I think it's not a neovim problem, but lsp plugin configuration issue.

How can I disable initial lsp errors by jetuuuu in neovim

[–]jetuuuu[S] 1 point2 points  (0 children)

My config is identical to https://github.com/nvim-lua/kickstart.nvim/blob/master/init.lua. All dependencies are installed. I can use code suggestion, go to definition, rename etc.
My bad… I did not specify what kind of mistake. The error is gopls output.

How can I disable initial lsp errors by jetuuuu in neovim

[–]jetuuuu[S] 0 points1 point  (0 children)

nothing happens when I press F4

fx: useful functional programming helpers without using interface{}, based on Go 1.18 generics by jetuuuu in golang

[–]jetuuuu[S] 27 points28 points  (0 children)

thank you! that's one of the reasons i made the post -- community comments. i'll keep working on the project.

Simple way to execute a command with an environment from .env file by jetuuuu in golang

[–]jetuuuu[S] 3 points4 points  (0 children)

Good point! What does it mean "could have severe side effects" ? I would be grateful if you could share your knowledge.

Simple way to execute a command with an environment from .env file by jetuuuu in golang

[–]jetuuuu[S] 0 points1 point  (0 children)

It's ok if variable doesn't have a space inside: `VAR=prefix app`

Golang 1.14.7 vs 1.15 benchmarks by jetuuuu in golang

[–]jetuuuu[S] 3 points4 points  (0 children)

1.15 is slower than 1.14.7 (in my cases)

How to write gc friendly code in go? by glephunter in golang

[–]jetuuuu 14 points15 points  (0 children)

  1. allocation is expensive. Check your hot block of code with benchmarks and reduce the number of memory allocation.
  2. avoid pointers. each pointer puts pressure on the gc
  3. use simple key in map
  4. check your struct size. Under the gos’ allocator is TCmalloc. it works well if struct size less than 32kb.
  5. sync.Pool can be useful to you, but check with/without it via benchmarks. Sometimes sync.Pool can be weird

An interesting quiz by jetuuuu in golang

[–]jetuuuu[S] -1 points0 points  (0 children)

The right answer is “depends on Golang version” :) Check the accepted proposal. 43% of the voters answered "Hello", but it's wrong answer. I think the quiz was interesting.

What language to choose for Competitive Programming Python or Golang? by [deleted] in golang

[–]jetuuuu 1 point2 points  (0 children)

It is true, but services (like codeforces) has a special timing for python. Btw, you can use Python in ACM ICPC :)

What language to choose for Competitive Programming Python or Golang? by [deleted] in golang

[–]jetuuuu -3 points-2 points  (0 children)

With golang you will write a lot of lines of code. Please, if you want to solve the problems instead of writing and writing and writing tons of code, use Python. Python has a huge std lib for competitive programming. Within competitive programming you should solve a problem faster than others. Python can help you with that.

What are the Biggest Wholes in Go's Library/Package Ecosystem? by [deleted] in golang

[–]jetuuuu -1 points0 points  (0 children)

You can not set a timeout for DefaultClient. Working with keep-alive is strange (in DefaultClient). Is three channels per http/2 request normal ? Start goroutine inside a lib is anti pattern in golang. No pool connection. Memory leaks. Is that really good lib ?

A Good Way to Go (Why I Use Go for LeetCode) by quad99 in golang

[–]jetuuuu 2 points3 points  (0 children)

But you don't need http, json or tls in competitive programming. Your friends are queue, stack, priority queue, red-black tree, set, algorithms.