Floating precision in rasterio.windows.from_bounds about rasterio HOT 2 CLOSED

@adehecq windows have float offsets and dimension. They're primarily for use with GDAL. They must be rounded if you want integers that can be used to slice an array.

from rasterio.

@adehecq windows have float offsets and dimension. They're primarily for use with GDAL. They must be rounded if you want integers that can be used to slice an array.

Thanks @sgillies. Yes, I'm aware that windows have float offsets and dimension. Sorry if that was not clear, but what I meant is that the output is incorrect. The function returns a height of 3022.0000000000005 whereas it should be exactly 3022.
This is caused by floating precision. windows.from_bounds uses transform.rowcol underneath, at this line. In the example I gave above:

rows, cols = rio.transform.rowcol(transform, [left, right, right, left],[top, top, bottom, bottom],op=float,)

yields "rows = [0.533333333333303, 0.533333333333303, 3022.5333333333338, 3022.5333333333338]". Due to floating precision, the left term has 15 decimals and the right one 13. I don't know if there is a way to overcome this precision issue? Maybe by allowing a fixed number of decimals?
This floating precision issue has caused me a lot of troubles with many other rasters...

from rasterio.