docs: gno does not support shadowing native types

[deelawn]

closes #1091

This is a simple documentation update to clarify that gno does not support shadowing native types. I've discussed with @jaekwon and this is not something we want to support.

[leohhhn]

Makes sense 👍

[thehowl]

BTW to fully close #1091 I suggest we catch the error explicitly and return a useful error message (currently, the fact that we don't allow shadowing native types seems accidental).

[deelawn]

BTW to fully close #1091 I suggest we catch the error explicitly and return a useful error message (currently, the fact that we don't allow shadowing native types seems accidental).

Sounds good. I modified the error message that gets returned when this happens.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 47.47%. Comparing base (d32b583) to head (38a5b53).
Report is 3 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1711   +/-   ##
=======================================
  Coverage   47.47%   47.47%           
=======================================
  Files         385      385           
  Lines       61376    61375    -1     
=======================================
  Hits        29139    29139           
+ Misses      29802    29801    -1     
  Partials     2435     2435           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[deelawn]

Still good with this @leohhhn?

[leohhhn]

@deelawn should it be "built-in"? Otherwise just the capitalization on language names.

[thehowl]

Sorry for the back and forth, should have checked earlier, but I guess the closest term to what is on the Go spec is predeclared. The spec still uses built-in, however in relation to functions.

I guess that also raises the question of whether built-in functions are also considered predeclared, and hence not shadowable, or not.

[deelawn]

Sorry for the back and forth, should have checked earlier, but I guess the closest term to what is on the Go spec is predeclared. The spec still uses built-in, however in relation to functions.

I guess that also raises the question of whether built-in functions are also considered predeclared, and hence not shadowable, or not.

Should we bring this up during the PR discussion meeting or just change the name to predeclared? I don't have a strong opinion on this.