But are you gonna return something for this method??? You said you’d return an integer, yet there is no return statement!
and it had better be an integer! it had better be an integer, motherfucker!!
Compiler/interpreter: Can’t find variable
farfignewton.Earlier:
Me: Declare variables
near, farIDE: Oh! You mean
farfignewtonright? I found that in some completely unrelated library you didn’t write. Allow me complete that for you while you’re not paying attention.IDE is one thing, Go refuses to compile. Like calm down, I’m going to use it in a second. Just let me test the basics of my new method before I start using this variable.
Or every time you add or remove a printf it refuses to compile until you remove that unused import. Please just fuck off.
VSCode with Go language support: removes unused variable on save “Fixed that compilation bug for ya, boss”
Like actually deletes them from the working copy? Or just removes them in the code sent to the compiler but they still appear in the editor?
Yeah IIRC it deletes them, which is as mad as you would expect. Maybe they’ve fixed that since I used it last which was some years ago.
I’m not a CS major but why exactly does having a variable or parameter that’s not used in C, C# and C++ throw a warning
Me: <starts a heredoc>
jetbrains: This heredoc goes on FOREVER!
Me: I’m going to close it…
jetbrains: <dies>
