Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API

From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
This post was tagged "my name is the annihilator your anal cavity shall be devastated".
devRant doesn't seem to like my tags. -
Is this your brain on Rust? Then you use the ref in your code, and it works fine until the prod build because it turns out it was cleaned up at the end of the function ;P
-
@BordedDev No, this is Patrick.
By which I mean octopusdog.
By which I mean dear uncle Bjarne Stroustrup hypothetically penetrating humanity's figurative asshole with a sawed-off shotgun; much harder to do in ceeploosploos, but when you do, oh boy, does it blow off your entire digestive tract, huh?
Oh, God, why can't it just be a damned fucking pointer! -
iiii93553dconst auto&& would have worked better in the case you're not sure it's a ref or a value returned, i believe
-
@iiii I'm not really at freedom to change much as it's not my code, so I can't really do shit my way. That's where the confusion and frustration comes in.
-
I'm amazed you need to lint python but it kind of makes sense
It would slow things down if you had to preexec all the code with variable return types etc
fknshit. Am I stressing about linting and formatting moreso than what the code itself does or is it just another hallucination?
I call it correctness paranoia. Bitch does it even compile. Yes, perhaps, but I absently-minded added a single newline somewhere, and that's no good.
So re-read the diff again: oh.
const auto&
should be
const auto
probably.
F is not returning a ref...
Should it return a ref?
Fuck, I'm declaring this nonref, should I
T N(V)
or
T N = V
Plain old doesn't fucking matter most of the time, but what if I missed a detail somewhere and so it *does* matter here?
REREAD. AGAIN.
SLOWLY.
DYING.
DYING.
DYING.
rant