looks good to me
looks good to me
looks good to me
undefined
if (error) { continue; }
undefined
try { operation(); } catch { // nice weather, eh? }
☑️ PR Approved
Thanks. I hate it.
undefined
with contextlib.suppress(BaseException): do_thing()
On Error Resume Next
Visual Basic is a beautiful language
undefined
On error goto 0
Was always syntacticly confusing for me.
I legitimately use this line in one of my scripts because range.find returns an error of the value is not found. The use case is taking a 2d matrix saved as an array, with data collected from multiple excel tabs and rearranging it for a CSV upload into Salesforce. The initial array contains values that the rest of the data does not have, so when I search for a non existent value, I can skip the error.
Of course vba COULD just implement try/catch statements and that'd be so much cleaner, but alas.
If I can't see it, is it really there?
If it wanted to get my attention it should have been an error
If it works, it works
I would add: until it doesn't.
This is why:
"It ain't stupid if it works."
is fundamentally incorrect.
Sometimes it’s better to hope while closing eyes
Warnings are for ignorings :3
Eh it's Javascript. Anything goes
this is fucking gold
Yeah, array.length is mutable in javascript. I'm surprised it caught on.
If i can just suppress the warnings which need to be fixed till morning in my buggy code, anything goes!
Warnings? We’ll come back and address those later. Maybe once we’re feature complete. Or maybe shortly after that.
Don't worry. We'll totally fix all of them soon. Promise. Hand to God. They definitely will not be here five years from now.
Meanwhile in another universe one of my biggest win was to introduce this line in our PR validation pipeline.
undefined
eslint . --max-warnings 0
Works so well, and soothes the warning annoyance brain, and keeps warnings from eventually becoming errors.
Actually fixing warnings is for noobs
if they mattered they'd be errors I'm sure
That's when you do CTRL+C, CTRL+V
I, too, place 2> /dev/null
after every line
Yes, but 2>&1 > /dev/null
is the real hero.
No, > /dev/null 2>&1
is. If try your example but with file instead null, stderr content not in file.
Because x>y not redirect x to y, but duplicate y and set x to y-duplicate. See bash manpage REDIRECTION (your example in that section for what not work).
As i understand, your example set 2 to what 1 is, then set 1 to null. Now 2 not null, but what 1 before.
-ErrorActionPreference SilentlyContinue
--yolo
edit: works better when used together with StackOverflow.comment.enabled = false;
I don't get it. This isn't funny. I wouldn't approve it in merge request. Most wouldn't.
Trying to hide problems and incompetence is the joke. A lot of people don't want problems solved, they just don't want to see them, and will take the easy route. If you just want that, this is the easy route.
Incompetent? Absolutely, that's the joke.