mirror of
				https://github.com/ethereum/solidity
				synced 2023-10-03 13:03:40 +00:00 
			
		
		
		
	Update types.rst
This commit is contained in:
		
							parent
							
								
									77e4f9c8fc
								
							
						
					
					
						commit
						3594f973df
					
				| @ -557,7 +557,7 @@ So ``bytes`` should always be preferred over ``byte[]`` because it is cheaper. | ||||
|     that you are accessing the low-level bytes of the UTF-8 representation, | ||||
|     and not the individual characters! | ||||
| 
 | ||||
| It is possible to mark arrays ``public`` and have Solidity create a :ref:`getters <visibility-and-getters>`. | ||||
| It is possible to mark arrays ``public`` and have Solidity create a :ref:`getter <visibility-and-getters>`. | ||||
| The numeric index will become a required parameter for the getter. | ||||
| 
 | ||||
| .. index:: ! array;allocating, new | ||||
| @ -806,7 +806,7 @@ Because of this, mappings do not have a length or a concept of a key or value be | ||||
| Mappings are only allowed for state variables (or as storage reference types | ||||
| in internal functions). | ||||
| 
 | ||||
| It is possible to mark mappings ``public`` and have Solidity create a :ref:`getters <visibility-and-getters>`. | ||||
| It is possible to mark mappings ``public`` and have Solidity create a :ref:`getter <visibility-and-getters>`. | ||||
| The ``_KeyType`` will become a required parameter for the getter and it will | ||||
| return ``_ValueType``. | ||||
| 
 | ||||
|  | ||||
		Loading…
	
		Reference in New Issue
	
	Block a user