วีดีโอ

Yes! They are similar in some ways, but they do have different implementations and functionality under the hood.

Thank you and I am not using vsc. I am using Zed here with the GitHub theme. However, the GitHub theme should generally be available in vsc as well.

Thank you :)

Absolutely! There are clearly multiple ways. I was just demonstrating the rune functions we can use to solve this problem. Feel free to see the other comment as well, where a similar approach was mentioned :)

@@shinsoking5816 that’s a cool attitude and I wish you the best of luck. I have been doing golang a few years and am quite proficient now, but I never take anything for granted, that’s why I still like to watch good content producers like Flo because there’s always something new to learn. One quite confusing area is error handling. It may seem quite simple at first but it easy to get it wrong if you don’t understand the fully error handling eco system. In short, never ignore an error from a function without being sure it’s safe to do so (there’s always an exception to the rule). Wrap errors when possible. Understand errors.is and errors.as. I didn’t fully understand this until fairly recently so I’ve had to enterly rewrite many of my packages to perform error handling properly.

Have fun, and enjoy the time learning! We are always here to answer any questions you might have! @dawnrazor thank you and lovely suggestion!

I also forgot to mention don’t panic, return error instead and don’t be lured into using MustXXX methods that by convention panic that some packages provide. The reason is concurrency. There is only 1 reason that I know I of when panic is ok and that is when checking something against being nil because dereferencing would panic anyway and panicking with a useful message is better than getting an anonymous/generic message

I don't have an answer on that, but I've noticed the use of signed integers for data that is strictly unsigned is very common across many languages, libraries, SDKs, and systems. So much so that often, when I am designing a data model, using signed is necessary for interoperability to not be a total headache. I wouldn't be surprised if the choice was made in that context.

Good question! So first all unicodes are obviously non-negative. In addition to @orterves comment, there can be two additional reasons: 1. `int32` allows for negative assignments, which can represent error conditions or initial values (also commonly used for string operations). 2. `int32` can represent all unicode codepoints without needing the full range of `uint32`.

I get your point and your confusion! So, the editor I am using has automatic line wrapping enabled, which means that the lines are automatically wrapped for visual help. If you look closely at 14:33, the lines that are actually lines are highlighted with a lighter color. In the end, the explanation is correct because it's really only two lines: ```go text := `Hello, 世界! This is a test. Here's some text with uppercase and lowercase letters, and even some emoji: 🚀 And here's a line with no words to test line counting.` ```

The reason that confused all of us, is the word-warp of the editor. Notice what is hightlighted when the cursor is on the line. Its very subtle but its there. What I really got me confused is the line count method. Why don't just len(strings.Split(" "))-1?

Or even better, in the for range loop, if r == ' ' { ta.lineCount++ }

​@@stavroskois9656 your method also works and is much simpler. I just wanted to demonstrate the runes function, but yes, you are definitely correct. There is no need for that, and the line endings don't have any special multi-byte characters. You could also use `strings.Count(text, " ")`. Thank you for bringing this up - it's a great reminder that sometimes the simplest solution is the best one!

@@stavroskois9656 ok great thanks. This was doing my nut in!

Already answered in the other comment, but thank you :)

Happy to hear that! Hopefully, more learnings to come for you :)

I am glad to hear that. It's lovely that you understand things more clearly now!

Sure thing :)

I am using the Monaspace font :)

Thank you! I am using the Monaspace font :)

@@FloWoelki great. thanks for the reply.

1. Well it's really similar to this described issue on GitHub: github.com/MariaLetta/free-gophers-pack/issues/3 2. I do communicate with the official Go team 3. I do have a copyright notice mentioning that the Gopher was inspired by the original author

Lol wtf dude?are you the creator of the logo or something? Otherwise why you riled up like that?

@@SaiyanJin85 no but for better or worse i give a shite about people respecting other people’s work it’s not a big ask to tell the man to follow a simple rule. It’d be a crummy world if people only looked out for themselves, as you suggest.

​@@pookiepats I get it but honestly you over reacting. You literally you came out of your way to "defend" something that isn't even yours in a rudest way possible and you didn't even apologize when you got your response from Flo. Also about your charitable nature I hope you do that for real problems as well and not for that "first world problems"...

who gives af you nerd lmao maybe you can complain to hr *gives atomic wedgie*

Thank you :)

I thought the same thing myself when I first started programming Go (from C++) see my comment above regarding the TH-cam channel "Boldly Go" it will make sense

That's so true, and I get your point! I'm not entirely sure what the reason was for this decision. Maybe it's just a use case you use less often.

Thank you, I really appreciate it!

Glad it was helpful! :)

Welcome, and I am glad you like it :)

Hehe gotcha! Thank you so much for watching :)

Thank you, man :)

Thank you for watching! :) Greetings back!

It is a highly requested one. It will be there soon :)

Thank you man :)

Thank you! :) Sure thing, I can make a video about that. Do you have any specific questions in mind?

@@FloWoelki Thanks. Just the way one should organise real world go projects and project structures. stuffs like go.mod file, naming test file with x_test.go, importing functions etc, are new to me despite solving 100+ leetcode problems. I am sure, I don't know many such rules. Would be nice to have a single video which collates all such arbitrary rules.

I'll write it down; thank you for the suggestion

Thank you :)

I see what you did there 🤣

I hope it was worth the time watching :D

Honestly, I do think that some people will create their own iterators for their libraries because they give you a lot of flexibility and developer-friendliness. Clearly, I cannot predict the future, so let's see where it goes :D

Well, it's kind of a vibe :D It should be relaxing and enjoyable to watch the video. Usually, I just have some music at the beginning and at the end of the video.

Glad you like them! :)

That's the spirit :D