You're likely looking for the OrderBy method instead.

If you Google "linq order enumerable" you'll find this kind of information easily :)

C# experts is it that normal i have this message with System.Linq, System.Collections and System.Collections.Generic directives included in my solution ?
error CS1061: 'IEnumerable' does not contain a definition for 'Order' and no accessible extension method 'Order' accepting a first argument of type 'IEnumerable' could be found (are you missing a using dire

Maybe add tag "combinatorics"?

Took me more time than I thought it would, but enjoyed it. Kudos to the author.

ditto. I also targeted a wrong format. Besides, I think this kata should be moved to the 7 kyu category at least.

Noticed that case as OK in description!

It'll rerun the tests and only invalidate solutions that fail.

Thank you!

If I modify tests, will it invalidate only those which does not accepted by new tests?

Or it will just invalidate all previous solutions?

I use comma-ok idiom in this translation. There is no need to return a value and error (comma-error idiom).
However, output format should be specified as value, ok in the description and/or solution sample

I did some reading, and Go seems .. special.

There is no idiomatic empty value, strings cannot be nil, and functions often return "a value and an error." The current initial code seems to return a value and a valid flag instead.

Please do not expose non-Go programmers to this madness. Use language-specific blocks in the description. Also, specify the output format of the function correctly and completely for your 7 kyu solvers.

"Extra modifier tests" in all currently available languages call "xxxs" "4-extra small" ( and large ). That should be "3-extra small" ( and large ).

( Go )

0, false for Go

Pick one and stick with it. I don't know if Go has an idiomatic empty value, but neither 0 nor false actually looks like it.

Why couldn't a negative size be valid? That would be a completely artificial restriction on the number of allowed xs before s.

There should be one more condition added on the 0 and negative values being unacceptable. I though it was implied, and ran into a couple issues. Either add such cases to the testing pool and the description, or do not accept negative values. How can a valid size be negative?

challenging, but such a relief when it finally resolved all the tests. I would rate this kata higher than 6: even though the final solution is simple, it takes some time to arrive at it.