What problem does this solve or what need does it fill?

While working with a folder handles, I needed to extract paths of all handles from inside the folder, and pass them into an external function to process. For performance reasons, I wanted to avoid unnecessary cloning of paths, and originally wrote the code expecting to pass around an iterator of &Path, but when I started implementing asset handles logic itself, I faced with an issue that AssetServer::get_path returns an owned instance of AssetPath, preventing me from getting &AssetServer-lifetime reference to asset paths, and forcing me to do cloning (for potentially thousands of files)

What solution would you like?

Some sort of method to get AssetPath by reference, instead of an owned instance.

Example impl:

    pub fn get_path_ref<'a>(&'a self, id: impl Into<UntypedAssetId>) -> Option<&'a AssetPath> {
        let infos = self.data.infos.read();
        let info = infos.get(id.into())?;
        info.path.as_ref()
    }

What alternative(s) have you considered?

Cloning Paths into PathBufs, which is fine on smaller scales, but still incurs a non-zero cost when working with large handles amounts.