justforfunc #37: sync.Pool from the pool 

I was about to comment the same thing.

Sure, I actually wanted to make sure people didn't get the idea that pools are magic and you should use them everywhere (they're not) I'll add the new episode somewhere

I also think that in this example it's better to use var data pullRequest Since it could be allocated on stack and stack memory is much faster than heap and does not require GC at all. However, judging by allocations, even in such a simple example, the compiler decided to allocate this memory on the heap. It would be interesting to know why.

Exactly!

Waaaaaaat, that's amazing 😮

Now I need to buy humongous sunglasses

I agree! It should still be summer when the next episode of JustForFunc comes out :D

Add this to your ~/.bashrc file: alias whoseport="lsof -i -n -P | grep $1" The command will slightly differ if you're not on a Mac.

A linux version fwiw whoseport() { PID=$(sudo ss -H -p -l -4 "sport = :$1"|sed "s/^.*pid=\(.*\),.*$/\1/") ps w $PID }

thanks man =)

➜ which whoseport whoseport () { lsof -i ":$1" | grep --color=auto --exclude-dir={.bzr,CVS,.git,.hg,.svn} LISTEN }

Really thanks man, it will be useful a lot, I didn't know that.

The webhook always contains the field, so resetting it is unnecessary But it wouldn't hurt to set it to 0, or even keep the *int and set it to nil (one extra allocation)

JustForFunc: Programming in Go ah I see. Thank you for a great video.

Well, you take something, write into it, read a value and return it back to the pool. The data you wrote into it, is still there, so the next function that uses the pool might get a pre-filled object and if it does not validate it correctly you run into issues. Usually pools are used for things like buffers where you rent a []byte, write into it and use it like this written := w.Write(buf, []byte("Hello! .... x100")) // this could be a serializer that reuses the given array val := r.Read(buf, 0, written) return val

thanks,

It's really nice seeing a comment from a familiar name :D Hi Komu!

Usually that's for the json package to put nil in the field when it's not in the payload.

So that you can differentiate between a integer coming as 0 vs the integer not coming at all in the payload

That's exactly why

Subhojit Dutta damn that’s crazy thanks for the info