From: arne@vajhoej.dk   
      
   On 8/19/2025 11:19 AM, Chris Townley wrote:   
   > On 19/08/2025 16:10, Arne Vajhøj wrote:   
   >> On 8/19/2025 10:09 AM, Dan Cross wrote:   
   >>> Whether integers are signed or unsigned by default is not   
   >>> terribly interesting to me, but I do believe, strongly, that   
   >>> implicit type conversions as in C are a Bad Idea(TM), and I   
   >>> think that history has shown that view to be more or less   
   >>> correct; the only language that seems to get this approximately   
   >>> right is Haskell, using typeclasses, but that's not implicit   
   >>> coercion; it takes well-defined, strongly-typed functions that   
   >>> do explicit conversions internally, from the prelude.   
   >>>   
   >>> But that's Haskell.  For most programming, if one wants to do   
   >>> arithmetic on operands of differing type, then one should be   
   >>> required to explicitly convert everything to a single, uniform   
   >>> type and live with whatever the semantics of that type are.   
   >>>   
   >>> This needn't be as tedious or verbose as it sounds; with a   
   >>> little bit of type inference, it can be quite succinct while   
   >>> still being safe and correct.   
   >>   
   >> Kotlin is rather picky about mixing signed and unsigned.   
   >>   
   >> var v: UInt = 16u   
   >>   
   >> v = v / 2   
   >>   
   >> gives an error.   
   >>   
   >> v = v / 2u   
   >> v = v / 2.toUInt()   
   >>   
   >> works.   
   >>   
   >> I consider that rather picky.   
    >> Ada as nearly as bad, although that would work, It relies on the   
   > programmer making an explicit conversion   
      
   Just for the record then I do not consider it bad.   
      
   Arne   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)