People will keep using that SO question as an kata idea until some day, some time, one of them managed to get through. Which isn't that unlikely given how fast beta process is nowadays. (And then we'll mark the ones after that duplicates anyway.)
just as a feedback (I know it wouldn't matter at this point), but would be much better for read to return array of bytes (think Buffer) and write should write bytes as well, meaning a value bigger than 255 take more than "one allocated memory". with write(0, 'aaa') to allocated(4) would then return ['a', 'a', 'a'] on read and write(0, 'ababab') would either throw (aka buffer overflow) or return "safely allocated data", like ['a','b','a','b']. It would be much closer to a real memory pointer management IMHO
seems fixed, Node 18+ is enabled and older versions are not selectable anymore
Use Node 8, it doesn't work on Node 10
Too late to change the requirements.
People will keep using that SO question as an kata idea until some day, some time, one of them managed to get through. Which isn't that unlikely given how fast beta process is nowadays. (And then we'll mark the ones after that duplicates anyway.)
And there's now a Java version of the same SO question too. You can definitely expect people to do the same thing too!
Please unpublish this umpteenth duplicate.
NO, asking for
4in addition totrueandfalsedoes not make it original.Not to mention https://www.codewars.com/kata/may-a-equals-equals-1-and-and-a-equals-equals-2-and-and-a-equals-equals-3/ , which came after Schrödinger's Boolean.
Also, Schrödinger's Boolean wasn't the first by far either.
I agree.
Looks a lot like Schrödinger's Boolean
Where to start?
Edit: Got it...
generateRandomBinaryDataandgenerateRandomReadableStringsdoesn't exist in Typescript (not available inglobalnor as an import)just as a feedback (I know it wouldn't matter at this point), but would be much better for
readto return array of bytes (think Buffer) andwriteshould write bytes as well, meaning a value bigger than 255 take more than "one allocated memory". withwrite(0, 'aaa')to allocated(4) would then return['a', 'a', 'a']on read andwrite(0, 'ababab')would either throw (aka buffer overflow) or return "safely allocated data", like['a','b','a','b']. It would be much closer to a real memory pointer management IMHOdone!
It should be clear now ;-)
Please update the description to indicate that quotes and backticks are banned as well ;-)
Edit: and
evaldone, it should be pretty different from the "Hello World!" one, since I disabled operators as well
the error message is pretty clear on what went wrong now
Loading more items...