You are so full of yourself. You are in no position to tell people what they should and should not be proud of.
Linq is the worst thing a beginner coder could ever learn.
And who told you that OP, or anyone in this thread as a matter of fact, was a beginner? Everybody knows what 2.5x faster means. You didn't need to recite the entire hare and tortoise song-and-dance like you're talking to preschoolers. People know when they're being patronized, so have some tact.
Since you're so intent on quoting things, want me to leave off with something?
Premature optimization is the root of all evil.
If LINQ is not a bottleneck, it is not a bottleneck. You are Dunning-Kruger personified.
I hope it's not a solution you're proud of. Linq is slow as a sloth in a tarpit. Very slow. Your code, while short (and maybe cool looking to those who care about looks over performance), is over 2.5 times slower than my plain, ordinary, "normal" algorithm.
It's like if our code was in a race around a track, mine would go around more than 2 and 1/2 times before yours went around even once.
Linq is the worst thing a beginner coder could ever learn.
one of the tests contains not existing char a probably it should be d instead
fight = mpadd*p*dzz**wswsqb*
if it would be mpddd*p*dzz**wswsqb* in this case result should be like expected
yes, once again I was too eager to attempt and a silly bug (; after an if statement) was the problem.
I now understand that there is the possibility that attempt and test don't always have the same result.
Thanks for the links
This is cool!!!!!;)
This comment is hidden because it contains spoiler information about the solution
.
good, you're on the right track
Everyday I learned bizzare stuff from here
thanks guys, my bad
You probably confused
dandb?No, d is on right side.
You are so full of yourself. You are in no position to tell people what they should and should not be proud of.
And who told you that OP, or anyone in this thread as a matter of fact, was a beginner? Everybody knows what 2.5x faster means. You didn't need to recite the entire hare and tortoise song-and-dance like you're talking to preschoolers. People know when they're being patronized, so have some tact.
Since you're so intent on quoting things, want me to leave off with something?
If LINQ is not a bottleneck, it is not a bottleneck. You are Dunning-Kruger personified.
I hope it's not a solution you're proud of. Linq is slow as a sloth in a tarpit. Very slow. Your code, while short (and maybe cool looking to those who care about looks over performance), is over 2.5 times slower than my plain, ordinary, "normal" algorithm.
It's like if our code was in a race around a track, mine would go around more than 2 and 1/2 times before yours went around even once.
Linq is the worst thing a beginner coder could ever learn.
Read the description again. There are letters that don't have point values assigned to them.
From the description:
one of the tests contains not existing char a probably it should be d instead
fight =
mpadd*p*dzz**wswsqb*if it would be
mpddd*p*dzz**wswsqb*in this case result should be like expectedyes, once again I was too eager to attempt and a silly bug (; after an if statement) was the problem.
I now understand that there is the possibility that attempt and test don't always have the same result.
Thanks for the links
See this paragraph, this paragraph, and this paragraph.
Loading more items...