is it this type of floor as operation same as floor() funtion from the module Math? or it only serve for this purpose? example: you have 2.5 it only gives you 2 as a floor. then f you need to rount up or down then should be the time to use ceil and floor methods?
In factor, the acceptance tests sometimes expected a whole-number result to be given as an integer, and sometimes as a float with zero fractional part. I had to ATTEMPT several times until the (randomized) tests were happy with my "integerized" results.
best answer
WHAAAT..I could never have done that
done
x,D
is it this type of floor as operation same as floor() funtion from the module Math? or it only serve for this purpose? example: you have 2.5 it only gives you 2 as a floor. then f you need to rount up or down then should be the time to use ceil and floor methods?
This comment is hidden because it contains spoiler information about the solution
got: '132081019.20' expected: '132081019.2'
got: '125797416.00' expected: '125797416'
In case of one test this one is good !!!
Why you not check a != 0 and b != 0?
You clearly understood the fundamentals :)
if you recall the boolen expressions.
True and True automatically return True
True and False / False and True return False
Its smart
In factor, the acceptance tests sometimes expected a whole-number result to be given as an integer, and sometimes as a float with zero fractional part. I had to ATTEMPT several times until the (randomized) tests were happy with my "integerized" results.
on submit it gives you some surprise ;)
simple and clear!
And some of the expected values are integers, so comparisons with floats fail as well. I don't think this can be completed with Factor.
Loading more items...