Literally it's all you need to read to understand how maps work (though quite hard to get through, but defenetly worth it)

For Golang on passing random tests there's two test cases where both arrays are empty, and in one case it's required true, but false in another (see below)
So you couldnt pass "attempt" button with either coding both arrays to be zero as true, or coding one of array to be zero as false (which would cover any empty array presented as false).
Because either one or another test case will fail in this way

1st case:
---START---
array1: []
array2: []

Test Failed
Log
Expected
: false
to equal
: true

2nd case:
---START---
array1: []
array2: []
[]
[]
Test Failed
Log
Expected
: true
to equal
: false

Hi Raihan,

Why are you calculating ^3 of each digit as (int(c) - int('0'))?
That's some bytes/runes claculation mechanics implies?

Can you please give some details?