Posts by UkiahSmith@mastodon.social
 (DIR) Post #ARRXhIS95XhgJptzGK by UkiahSmith@mastodon.social
       2023-01-08T17:48:53Z
       
       0 likes, 0 repeats
       
       @RL_Dane @brandont @hyde @tayweeFor me it wasn't so much unlearning as that helix has missing/different functionality. No '*' or '#' really broke my editing flow.
       
 (DIR) Post #ARRXhJhQSDWKBW3hia by UkiahSmith@mastodon.social
       2023-01-08T18:54:54Z
       
       0 likes, 0 repeats
       
       @RL_Dane @brandont @hyde @tayweeNo worries, we are all still vim noobs.In normal mode '*' searchs forward for the word under the cursor, and '#' searches backwards for the word under the cursor.Is a super quick way to jump around code.
       
 (DIR) Post #AZAr21kRTgHmfCbGBU by UkiahSmith@mastodon.social
       2023-08-28T01:27:35Z
       
       0 likes, 0 repeats
       
       @grumpy see, I'm not hoarding.
       
 (DIR) Post #AqaKZbbKmL5NZZOFMW by UkiahSmith@mastodon.social
       2025-01-29T16:31:43Z
       
       0 likes, 0 repeats
       
       There was discussion about reducing the boilerplate of error handling for #Golang. I really did not like the options that were offered. They were confusing and limited in scope. I am happy to say that the proposal is not planned, and the issue is closed. I am pleased that the discussion took place, and that the Go community was able to look at options for improving the language overall.https://github.com/golang/go/issues/71203
       
 (DIR) Post #AqcJsvcqqCkLXdfZoG by UkiahSmith@mastodon.social
       2025-01-30T01:41:32Z
       
       1 likes, 0 repeats
       
       @frosch @hisham_hm I prefer the if err != nil boilerplate too. It's rather obvious, but I don't find it overly distracting. My non-scientific view is that most people who dislike it don't want to actually handle the errors to begin with. They just want to throw them up the call stack as if they were exceptions. My opinion is based on reading social media and blog posts.