You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 2, 2022. It is now read-only.
In some cases developers are choosing not to use the table scope because it lacks an iterator or a lookup function. Seems like that is not a security concern. If not, if that were added I think we would get contracts that are a little easier to query (get_table_rows contract >>scope<<) and make use of that built-in index.
Kevin
It acts kind of like a sub-table name we have no way to iterate over tables either. Something to consider.
In some cases developers are choosing not to use the table scope because it lacks an iterator or a lookup function. Seems like that is not a security concern. If not, if that were added I think we would get contracts that are a little easier to query (get_table_rows contract >>scope<<) and make use of that built-in index.
Kevin
James
👍