Add limitation info about dynamic sized variable types

[sukanyaparashar]

This PR adds the point for mentioning the limitation of using dynamic sized variable types strings and bytes.

[dariaag]

@sukanyaparashar Looks good to me, I would just rephrase it a bit to make this long sentence clearer:

In Solidity versions before 0.8.15, there is a limitation when using dynamic-sized variable types, such as strings and bytes, as mapping values in functions invoked multiple times. This issue arises because reusing the same parameters of these types in transactions leads to increased consumption of Solana accounts.

[dariaag]

Looks good to me, I would just rephrase it a bit to make this long sentence clearer:

In Solidity versions before 0.8.15, there is a limitation when using dynamic-sized variable types, such as strings and bytes, as mapping values in functions invoked multiple times. This issue arises because reusing the same parameters of these types in transactions leads to increased consumption of Solana accounts.

[ephemerno]

Looks very nice!
Have just one question:
in 101: for (uint256 i = 0; i < 45; ++i) {
why do you use here i until 45?

[sukanyaparashar]

Looks very nice! Have just one question: in 101: for (uint256 i = 0; i < 45; ++i) { why do you use here i until 45?

It is just an example of an iteration

Looks very nice! Have just one question: in 101: for (uint256 i = 0; i < 45; ++i) { why do you use here i until 45?

This is a really good question! In Solana, each mapping entry corresponds to usage of one Solana account and there is a limit of using 64 Solana accounts in a single transaction. We have used the value 45 so that the usage of Solana accounts exceeds the 64 accounts limit in this case and it fails.

That means if there are 45 iterations, then because of double spending issue described in this case, the total accounts used in this transaction will be >64, i.e, 45 * 2 = 90 + 9 = 99 accounts (extra 9 accounts are added by default).

[ephemerno]

Everything is clear, thank you!