> The negative spin would be: how to spend a lot of effort to solve a problem you would never have if you didn't use rust. I can't totally disagree, I sometime

> The negative spin would be: how to spend a lot of effort to solve a problem you would never have if you didn't use rust. I can't totally disagree, I sometimes had this feeling during the implementation. Contrary to other languages, you can't always choose your trade-offs: memory-safety is in practice almost non-negotiable in Rust (you can use unsafe code locally, but you won't implement the whole application in unsafe), so everything else has to adapt. For example, in another language, I probably would have kept slice+stride to avoid many refactors. In the end, I am quite happy with the tiling structures API, but a lot of work (and [boilerplate](https://github.com/xiph/rav1e/tree/f1c43dbdc52016f67ecf333832e30d97763e8b91/src/tiling) https://github.com/xiph/rav1e/tree/f1c43dbdc52016f67ecf33383...) was necessary to implement them.