These mostly add very little and have caused problems for people,
nor does it make sense to require this when the underlying
computations are performed in floating-point arithmetic depending
on ratios of user-passed in image dimensions.
Arbitrary absolute epsilons here would just be garbage; we could
try and compute desired relative error bounds based on the
determined scale values, but this still leaves the questions of
what purpose this would even serve, which is unclear.
Leave the filter kernel asserts as comment for documentation
of what the behavior would be with exact math, but don't actually
bother asserting here.
Fixes issue #736.
STBIR_ASSERT(out_last_pixel-out_first_pixel<=(int)ceil(stbir__filter_info_table[filter].support(scale_ratio)*2));// Taken directly from stbir__get_coefficient_width() which we can't call because we don't know if we're horizontal or vertical.
STBIR_ASSERT(out_last_pixel-out_first_pixel<=(int)ceil(stbir__filter_info_table[filter].support(scale_ratio)*2));// Taken directly from stbir__get_coefficient_width() which we can't call because we don't know if we're horizontal or vertical.