Golang Linked List - Golang Data Structures

[@GolangDojo]

📝Get your *FREE Golang Cheat Sheet* - golangdojo.com/cheatsheet

[@stephenoginga5926]

understood

[@farzadmf]

Thank you for the great and engaging video. Small go nit suggestion: when using receiver functions, it's recommended to be consistent to either use a value pointer or a reference pointer. In fact, if you use mixed, go lint tools will complain.

[@GolangDojo]

I use golangci-lint which I heard is supposed to be strict, and nothing came up. Let me do some digging.

[@GolangDojo]

I'd imagine it's safer to pass by value and only use pointers when modifications to the data structure are needed. I asked around in the official Discord too and that seems to be the case. Also, golint is deprecated for what that's worth. Thanks for pointing this out!

[@farzadmf]

I have a bunch of checks being run on my Go code usually and maybe linting is fine and it's one of the tools showing me warnings about that. What you mentioned is 100% true (using pointer receivers when modifying something); it's the consistency that matters usually: if you have one function receiving a pointer receiver because it's modifying something, even the ones not modifying anything are usually changed to receive a pointer receiver. Of course if you find a link or something that says you can have a mix of receivers, please let me know

[@GolangDojo]

I honestly have no idea which is preferred and don't have strong preference on either. If the linter is complaining, I'd probably listen to the linter in use. I'll keep an eye out on this, and maybe even mention our conversation here in a future video comparing popular Goalng linters!

[@manpt123]

Thank you sir, when you said it took a day to create this video I immediately subscribed.

[@letsgetrusty]

This guy putting out movies

[@GolangDojo]

HAHAHA

[@alfredogrande2430]

everyone: array golang dojo: *awway* jk, love your tutorials keep it up!

[@GolangDojo]

You should've seen my older channels. My accent was way worse lol. And thanks!

[@patbateman-o4g]

Honestly great video, already understood the concept of a linked list, however, you solidified my knowledge and you explained this much better than any of my prior instructors even did xD

[@GolangDojo]

Glad it was helpful!

[@kaushikplays4676]

func (l *LinkedList) remove(value int) { previous := l.head for current := l.head; current != nil; current = current.next { if current.value == value { if l.head == current { l.head = current.next } previous.next = current.next break } previous = current } } I kept head as the placeholder for previous. Do you think this is wrong?

[@GolangDojo]

The best way to figure it out is write some unit tests ;)

[@linwei2906]

me too. func (l *linkedList) remove(value int) { /* if head.value = vlaue head = head->next */ if l.head.value == value { l.head = l.head.next } else { p := l.head iterator := p.next for ; iterator != nil; iterator = iterator.next{ if iterator.value == value { p.next = iterator.next } else { p = p.next } } } }

[@dcastro97]

great video man!!.. I think we missed up to write a method to get length of a linked list, right?

[@GolangDojo]

Nice catch :)

[@JC-jn9kp]

For linkedlist, How are we able to input multiple values? Like "string", "string", Int

[@Levelord92]

But isn't Add() operation is O(n) since we need to iterate over the whole linked list in order to insert new element to the back?

[@simonedandreta7883]

How would you write a unit test for a method that doesn't return anything? For example the add() method. Thanks!

[@GolangDojo]

Testing series on the pipeline!

[@simonedandreta7883]

@@GolangDojo I have written few methods on linked lists in Go along with tests, but I am looking forward to your series!

[@gwnbw]

17:34 whats that you use that package and method pops up if you hover over it?

[@koushikhridoy8180]

Please work on your English. It's difficult to understand. Great video though.

[@vanshajdhar9223]

Amazing long awaited series

[@GolangDojo]

More on the way!

[@lasfito]

Great content, man. Appreciate it

[@kaushik5055]

Was waiting for this series 😃

[@GolangDojo]

Here we go! :)

[@Levelord92]

I would also suggest to use strconv.Itoa instead of fmt.Sprintf for converting our value into string, since we decide to max out our performance with strings builder