Can somebody explain, why `(0F/0F).coerceIn(0F,1F)...
# announcementsp
Paul Woitaschek
05/27/2021, 8:36 AMCan somebody explain, why
(0F/0F).coerceIn(0F,1F)NaNz
Zan Skamljic
05/27/2021, 8:37 AMNaN cannot be mapped to range, as it's "*N*ot a *N*umber"
Zan Skamljic
05/27/2021, 8:38 AMregular math and comparisons don't work on it, so it can't really become a valid number, either 0 or 1 that you have
p
Paul Woitaschek
05/27/2021, 8:38 AMAs it's not coerced in that case shouldn't it throw instead?
s
spand
05/27/2021, 8:38 AMIt seems pretty in line with the usual behavior that all operations involving
NaNNaNspand
05/27/2021, 8:39 AMNot sure anything involving
NaNp
Paul Woitaschek
05/27/2021, 8:40 AMNaN was never helpful and is a bug in every single case I faced it 😕
z
Zan Skamljic
05/27/2021, 8:41 AMas for throwing, that's java behavior, where it throws when you divide something by zero
s
spand
05/27/2021, 8:44 AM@Zan Skamljic No. Why dont you try it out.
z
Zan Skamljic
05/27/2021, 8:44 AMyes, actually
s
spand
05/27/2021, 8:44 AMThat is not the case we are discussing
g
gildor
05/27/2021, 8:44 AMBecause it’s int, float will return NaN
z
Zan Skamljic
05/27/2021, 8:45 AMmy bad, yeah, float seems to return NaN
g
gildor
05/27/2021, 8:45 AMThe reason of this behaviour is IEEE 754 and it’s widely adopted by programming languages and hardware
âž• 2
18 Views