It would be a blow to render this typing method slightly slower, definitely a deal breaker 😏
It would be a blow to render this typing method slightly slower, definitely a deal breaker 😏
I found those:
Underscore . . _ _ . _
Addition . _ . _ .
Subtraction _ . . . . _
Multiplication _ . . _
Division _ _ _ . . .
Equal _ . . . _
Right Parenthesis _ . _ _ . _
Left Parenthesis _ . _ _ .
But this isn’t enough for programming, square and curly brackets, carets, ampersand, pipe, tilda… I think it’s gonna be pretty challenging
And the Community rejoices at the perspective of your valuable contributions!
Don’t forget to look in which community this was posted
Agreed! Unfortunately these maddening behaviors were kind of set in stone several decades ago, and it has been (correctly) decided “Don’t break the web”, these weird quirks are kept in modern interpreters/compilers.
It’s actually quite interesting to read through the logic to follow when implementing an interpreter:
https://262.ecma-international.org/13.0/#sec-object.prototype.tostring
On the other hand, I don’t think you should add those ever
I found this, it looks like it’s not really possible because the structure of the two services are pretty different:
As a rule of thumb, I always put action verbs at the end of method names
LGTM
I love when there are solutions for every weird use case ^^