Ge;<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div class="h5"> - (fixed) type checker now validates if/while/for/until types<br>
<br></div></div></blockquote><div><br>I&#39;m not sure what this consists of, exactly. I thought it refered to the bug(?) that relates to a lack of overloading in operators like &quot;&amp;&amp;&quot;. To quickly re-explain the situation;<br>
<br>//this is valid (duh)<br>if (true) &lt;&lt;&lt;&quot;yay&quot;&gt;&gt;&gt;;<br>//so is this (relevant in detecting the start of the session or zero-length durations)<br>if (now) &lt;&lt;&lt;&quot;yay&quot;&gt;&gt;&gt;;<br>

//so I feel this should be too, yet it isn&#39;t<br></div></div>if (now &amp;&amp; true) &lt;&lt;&lt;&quot;yay&quot;&gt;&gt;&gt;;<br><br>I&#39;d argue that types like time and dur either have a truth-value or they don&#39;t and if they do have a truth-value then the logic operators should be overloaded to deal with them.<br>
<br>The quoted fix seems at least related to this phenomenon yet the reported bug isn&#39;t fixed.<br><br>could we go over what this fix consists of then, because now I&#39;m a bit in the dark about what we do have here.<br>
<br>Yours,<br>Kas.<br>