<blockquote>
<p>Range may reflect any mapping for that key from any point during the Range call.</p>
<p>Range may be O(N) with the number of elements in the map even if f returns false after a constant number of calls.</p>
</blockquote>
<p>The above is a quote from Golang.org documentation.
My question is regarding the usage of 'may be' and 'may'. Does 'may be' mean its not definite and its a possibility of that outcome or is there some other interpretation to it? Thanks in advance. </p>
<hr/>**评论：**<br/><br/>kune13: <pre><p>Values reported by Range reflect any mapping for that key during the Range call. There are no guarantees which mapping will be returned.</p>
<p>Range can be O(N) even if the user-provided function f returns false after a constant number of calls. Range copies dirty values and the effort for this cannot be controlled by returning false in f.</p></pre>Sythe2o0: <pre><p>Well, given there is a chance it could be O(N), that implies the worst case scenario is that it takes N time, or in other words, it's always O(N).</p></pre>
