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.
:D
Another thing to consider is that the object passed in the
items
parameter may handle indices differently than a standard list (maybe it doesn't support negative indices, for example). In that case, checking thatindex
is between-len(items)
andlen(items)-1
might lead to unexpected behavior.fixed
Thank you :)
I can't stands this no more ... forked and fixed!
Approved!
Yep, you're right. Lots of people around think "best practice" == "shorter".
Meanwhile, as a student we often have to balance between computer efficiency (may take some times/tests to get the more economical code) and human efficiency (throw a working solution in minute, letting the computer struggle with it). And this choice depends on criterias as different as available time, feeling, effort/reward ratio, previous problem, affinity, hunger/fatigue state, etc. =)
Hence, you sometime just want to do an humble and anonymous code solving it fast and go next, then see it highlighted because people confuse "state of art" with "straightness", "obvious" with "powerful"…
wouldn't be even better just trasversing only once and keeping a set handy to check if an item has already been seen?
The philosophy that dominates in Python is "It is easier to ask for forgiveness than permission". Many things in Python are implemented through exceptions, including every single iterator. They know when they've reached the end of the data because of a StopIteration exception being raised. They are designed to be performant enough that you can use them without too much worry, as long as the exception condition is still considerably less likely than the exception-free path. As always, it's recommended to use timeit to profile code if a section of code is performance-critical to determine what changes make a significant difference, but in general, a tight try and except block improves the reliability and sometimes the readability of code. Optimizations are being made all the time, and now Python 3.11's patch notes even claim that a try block that doesn't raise an exception is now "zero cost".
see issue above, plz.
Approved :)
Loading more items...