We probably should avoid hardcoding the backend version number in the path, as it makes it difficult to refer to library files in documentation.
One possible option (if we to enable the current and supported backends versioning) is to expose the versions directly in the library file. The library files, however, might become a bit cluttered. But we can also drop the support to older backend versions more frequently, so should be OK.
We probably should avoid hardcoding the backend version number in the path, as it makes it difficult to refer to library files in documentation. One possible option (if we to enable the current and supported backends versioning) is to expose the versions directly in the library file. The library files, however, might become a bit cluttered. But we can also drop the support to older backend versions more frequently, so should be OK.
All tests pass.