Consider keeping pixel-copying versions of ops in TransformNamespace
Open
- Dominant language
- Java
- Stars
- 94
- Forks
- 44
- PR merge metrics
- No merged PRs in 30d
Description
@ctrueden in a discussion about #433:
> We can debate whether to keep a pixel-copying version as `transform.scale` still.
Most of the ops in the `TransformNamespace` are nowadays wrappers for `Views.*`. `Ops.Transform.Scale` implemented a scaling operation that copied pixel-wise. With chaining it is possible to get a copy of the output of any `Views`-based transform anyway. But should we consider exposing convenience methods for `Input > Transform > Copy = Output`?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.