@NicoSchuele did you actually visit the link? it is the ONLY implementation that behaves this way. So no, it's incorrect. Sorry.