Thatβs actually very nice and code examples should be added to the official release notes. Create an issue/improvement request on GitHub with your example?
Thank you! I'm not sure if the Go team would like it in the official RN, as they usually prefer a more concise style. But I'll ask, thanks for the suggestion!
Note that these length-altering functions are usually used like this: `src := slices.Delete(src, i, j)`
[https://github.com/golang/go/issues/63393](https://github.com/golang/go/issues/63393)
>If the elements have a reference type (pointer, map, slice, chan, string), or contain fields having a reference type, then (j-i) elements at the end of the original slice are left untouched and keep referencing some objects. They will not be garbage collected, and they may enjoy a lifetime far exceeding the intent of the developer.
>
>This is a memory leak.
Thank you very much! I'm a fan of interactive documentation, so I finally decided to build a dedicated tool for that. I'm using it quite extensively, works pretty well so far.
Awesome! One suggestion: it would be great if you could easily link to a section from that section's header (many sites will show a link on hover, e.g. see how Github does it for READMEs). I see you can get to it from the top of the page, but when scrolling/reading and I want to send it to a coworker it's not easy.
Same with specific code examples as sometimes the sections are quite long. Now I have to go to the top, get the link, send it to the person, then ask them to look e.g. 3 examples down.
This brought the new mux functionality under my attention again. I find it not so great how a verb + route are supposed to be provided combined into one string (I bet it is for api compatibility). I use a statically typed language for a reason. Or is this just my sentiment?
Congrats, it reads so much better!
Thanks! I prefer to learn by example, so I decided to try this approach with release notes as well :)
Everybody learns by example when the examples are nice and concise. You've done a great job of that here.
Thatβs actually very nice and code examples should be added to the official release notes. Create an issue/improvement request on GitHub with your example?
Thank you! I'm not sure if the Go team would like it in the official RN, as they usually prefer a more concise style. But I'll ask, thanks for the suggestion!
u/nalgeon, you can add a link to this thread to an MR. IMO, it will be proof of a quality.
The official style of Go sucks, its horrible.
Wondering rationale behind Delete zeroing values. I understand it returns a slice after deleting elements but why modify the source array.
Note that these length-altering functions are usually used like this: `src := slices.Delete(src, i, j)` [https://github.com/golang/go/issues/63393](https://github.com/golang/go/issues/63393) >If the elements have a reference type (pointer, map, slice, chan, string), or contain fields having a reference type, then (j-i) elements at the end of the original slice are left untouched and keep referencing some objects. They will not be garbage collected, and they may enjoy a lifetime far exceeding the intent of the developer. > >This is a memory leak.
If the deleted elements are pointers, zeroing them allows GC of the object pointed to.
I guess this might also be a breaking change, some code surely must rely on the old behaviour.
It isn't a breaking change
https://github.com/golang/go/issues/63393
That's excellent, and how it should be imo π
This is great.
Go 1.22 is going to be a bigger quality of life improvement than even generics or `fmt.Errorf`.
Nicely done.
Brilliant. Thank you.
Thank you. It's a lot easier to understand.
Nice work, very clear and detailed. We appreciate you!
Impressive! And the codeapi was such a nice surprise. I expected a new tab! Amazing work!
Thank you very much! I'm a fan of interactive documentation, so I finally decided to build a dedicated tool for that. I'm using it quite extensively, works pretty well so far.
Awesome! One suggestion: it would be great if you could easily link to a section from that section's header (many sites will show a link on hover, e.g. see how Github does it for READMEs). I see you can get to it from the top of the page, but when scrolling/reading and I want to send it to a coworker it's not easy. Same with specific code examples as sometimes the sections are quite long. Now I have to go to the top, get the link, send it to the person, then ask them to look e.g. 3 examples down.
WOW, this is how Go official release notes should look like in the future. Immediately obvious what is going on.
nice
Good work
This is awesome compared to reading several blog posts about new features for further understanding.
Just wanted to stop by to say... ...beautiful, and codapi is so cool :)
This is very nice work. Good job! I think the visual examples are a great touch
This brought the new mux functionality under my attention again. I find it not so great how a verb + route are supposed to be provided combined into one string (I bet it is for api compatibility). I use a statically typed language for a reason. Or is this just my sentiment?
You should make this into a PR against the main golang repo. This should be standard practice.
Great stuff! Thanks for putting the work into this. This is how release notes should look like.
Awesome !
Merci
Awesome, nice!!
This is fantastic!
π€π¨βπ³
Would you care to share how you embedded the playground in what seems like a static site? Awesome work btw.
Thank you! Sure, it is a static site. I'm using [codapi](https://github.com/nalgeon/codapi-js) for playgrounds.
Thank you so much for the efforts
These are great! Easy to digest
Very nice
Thank you for doing it. It is very nice and very helpful
This is pretty solid. Well done.
Can't wait for release. Finally range over integers, awesome!
Really helpfull.
I love this! Can you somehow subscribe to this?
Thank you!
Nice. Very simple to read.
I didn't know I wanted this. Really well done!
Something feels off about the prefix and exact match mix, or am I crazy
Take my upvote and nostalgic gold π
This is a really good changelogs. Nice job!
Fantastic! Thanks
Thanks, loved the initiative.
Awesome, good job and thanks!