Loading collection data...
Collections are a way for you to organize kata so that you can create your own training routines. Every collection you create is public and automatically sharable with other warriors. After you have added a few kata to a collection you and others can train on the kata contained within the collection.
Get started now by creating a new collection.
Really? What if maxvalue in the given string has a negative value?
While it passes the tests without the Distinct, the instructions mention that duplicates are not allowed in some languages so many people are taking that as instructions to filter out duplicate entries from the first array.
And I was afraid my solution was gonna be jank and some Linq Master was gonna come along and laugh at me..
I can just imagine OP pulling an all-nighter wrangling with this problem over a 6-pack of Bawls Energy, hammering away at his keyboard while listening to Anime Hero music.
Imagine the smile on his face when all of those unit tests passed.
The sheer dedication is a best practice. OP never gave up, and despite the spaghettification, I raise my glass to him.
I love it
huh? Is there an explanation or is this trolling?
Okay so as I understand it this is an example of the "dynamic programming approach" to this classic challenge with a slight twist I still don't quite get. The classic approach might start with both current and total maximums equal to the first element. In each iteration it would compare the current element to currentMax + a instead of comparing it with zero. Aside from that, it's the same and you can Google it. So, why are you using zeros instead of elements? Does this always work?
Sure, but could someone explain it?
Thanks for showing me a new syntax! Much cleaner than building the dictionary inside the where clause, and probably about the same performance.
I'll never understand the tempatation to fit your code into as small a space as possible at all costs. Why in the world would you omit white space between symbols and sacrifice performance just to have the most terse answer?
This comment is hidden because it contains spoiler information about the solution
It's a very, very bad practice to put comments describing code that describes itself. The code is clean and self-explanatory. Why dirty it?
Loving this syntax.
This is very difficult to follow and extremely complex. Any reason in particular why someone would tick best practices? Is this revolutionary in its efficiency on large datasets or something?
Ugly as heck. Why on earth would you omit white space? Why would you want your solution to be extra cryptic and extra difficult to read? Not even going to critique beyond "this is hard to look at"...
Yeah what's the point of Distinct()?
Loading more items...