@d.w. Regarding login to chat: it's a somewhat arcane process. I noticed that you have to allow some Javascript from a domain that does not show up anywhere on SE, and only shortly during the login. So in case you use a blocker, try whitelisting everything for the login. Session timeout is quite long so you won't have to do that very often. Would be nice having you here!
@Juho Even mods can't impersonate users, and that's probably a good thing. :) Well, we can transform answers into comments, but not the other way round let alone create arbitrary post for any user.
One might argue that the restriction of determinism arrived late, and that they answer the (original) question insofar as algorithmic issues prevent effective testing.
@Gilles Did you deal with the flags on that question?
I'm confused that the Python question is still there.
@Juho On the other hand, we generally discourage edits that make lots of valid answers (valid in the sense that they fit a reasonable interpretation of the question) obsolete.
Well, since the question only says, "preferably, a deterministic algorithm", we might as well keep the answers.
Not sure about your answer, @Juho, by the way. It's a rather obvious bug looking at the code. My feeling is that it's an implementation bug. There is no reasonable idea behind the algorithm as is ("check if the words are equally long, and if they are if the last symbols match"). The reasonable idea refers to one that has another implementation.
It's definitely a cute bug, one that is horrible to find if you've written the code yourself, and as you explain passes many test cases. A bug, though.
Coin exchanges skrews our students every time. They even gave Greedy as an answer in the exam after they had explicitly shown that it was faulty in the exercises.
Jup. The hot question thingy is...troublesome at times. It brings attention to small sites, but it rarely seems to be the good kind. The entry metrics are probably broken ("many views and answers in a short time" does not happen on interesting questions, but on clickbait).
@Raphael I dealt with some of the flags. You can check the flag history on a post to know what flags were previously handled. What do you mean by “the python question”?
Q: examples of algorithms that work with casual tests yet are not correct A: numerically unstable algorithm, that works with some value ranges but loses precision in others
@Gilles Read the updated question, specifically item 1 in the "Specifically..." list. Implementation errors/bugs are not what he's after.
If the algorithm itself is the issue it might qualify, but the answer is not very clear on that.
Obviously, numerical algorithms should offer a rich class of examples. I'd guess D.W. is not interested in such (since they are rarely topic of basic algorithms classes, afaik) but he did not exclude them either.
Note also D.W.'s comment on the answer (which says "not a good example for my needs" but certainly doesn't "not an answer").
@Raphael If @D.W. is still having trouble logging in to chat, you might ask him to try a different browser. Chat login just completely stopped working from Chrome browser for me about two weeks ago. So I started logging in to chat using Firefox. Chat and Chrome combo may just be broken at the moment.
@Raphael It's an algorithm issue. The mathematical formula is correct, but not the floating-point algorithm. It isn't related to the choice of programming language. I wouldn't call this an implementation bug as opposed to an algorithm flaw.
You could say it's the implementation of real arithmetic using floating-point arithmetic, but I'd call this an approximation rather than an implementation
@Gilles Okay then. I'd have written the answer differently -- the Python thing seems tangential and an explanation of what the issue is is missing. But agreed, it can stay.
@Gilles I don't block js. And I've been using Chrome as my primary browser for several years. This is the second time in about a year that SE chat just started refusing to let me login using Chrome. The last time (about 6 or 9 months ago maybe?) the problem cleared itself after a few days. This time it hasn't.
It probably has to do with some cookies that Chrome stores in my Google account, because login stopped working on my machine at work, my machine at home, and my phone simultaneously.
But I can't figure out which cache to clear.
So I gave up and switched to Firefox.
(Which also seems to be handling my music streaming service far more robustly at the moment too.)