Short story: “number of characters” and “nth character” are more complicated questions than you might think when you deal with full Unicode text.
1,627 karma · joined July 21, 2007
Short story: “number of characters” and “nth character” are more complicated questions than you might think when you deal with full Unicode text.
I checked: neither // nor /// can be used as operators (syntax error: they both just start a comment). All your other examples work, but I would say those mean the author is intentionally trying to trick me. Or he’s writing a clever DSL, but that line is very fine and treacherous.
Example: the Olympus E-M10 has a 1,037,000 dots display, which means 345,600 pixels, which means 720x480. But all the marketing material (and review websites) reports “1 million dots display”.
“Chrome OS APIs, like Firefox OS APIs are not web APIs, so a Chrome OS app is not a web app, it’s just a regular app developed using web technologies.”
Things are different, no need to order them, especially on one single axis.
In other cases I’m also disturbed by the broken scrolling but in this case my only complaint is the space bar not working. This is a slideshow, but it feels like scrolling because it goes vertically and the scroll bar works. I’m pretty sure if the scroll bar were completely disabled and there was a [next] button with a different transition you wouldn’t complain because you wouldn’t think of it as broken scrolling, but just as another slideshow.
So, my suggestion to the author: make it slide horizontally.
xcrun swiftAlso: Rule 34.
For any given problem, only people who have not tried to solve it will say that.
When you do this by mistake and you don't know the hash you can find it using git reflog, which logs everything that happens in the repository.
More detailed: http://gitready.com/intermediate/2009/02/09/reflog-your-safe...