It's similar to the symbol for approximation which also is accurate for what it's doing cause the integer division approximates the actual value. So that's how I would remember.
But sure I guess you can also throw elephant trunk in there lol.
Don't mind me with my parseInt(22/7)
. The operator seems neat but I don't know if adding more and more operators to a flexible language is a good idea, this might not be clear to read.
Why not just Math.trunc(22/7)
, why convert to string and then parse it, risking getting scientific notation instead of normally formatted number?
parseInt(1000000000000000000000000 / 3) // => 3
Where did you see me convert it to a string? Also I just said the first working thing that came to mind.
More like tildeMostAbusedSymbol, sometimes it's an operator, an alias or a syntactic element. You know this little squiggle has caused a lot of people a lot of grief.
And sometimes it's the home directory
And it's almost impossible to type on a Czech keyboard!
I should build a language where you do database queries with ~/SELECT .... /~ and call it the elephant operator. The language would come with PostgreSQL bindings and nothing else, because elephants.