Joe Flint

It's now possible to implement this relatively easily with the new `Interceptor` chain infrastructure. Just wrap the `LegacyCacheWriteInterceptor` and skip calling it for responses you don't want to cache. Something...

@AnastasiaKubova while this would enable the workaround I mentioned above (really, it just eliminates the NSError construction), it doesn't exactly provide a clean and consistent way to reporting Swift errors....

It seems like these changes got applied directly to the 5.0 release branch, but weren't merged back into master. I renamed things to match the new class naming scheme.

Some context about why `pod repo update` doesn't pick up this change: https://github.com/CocoaPods/CocoaPods/issues/10229

#366 should have fixed this.

I would think so, but @freezy will know best. In the meantime, there is a test build here if you want to try: https://ci.appveyor.com/project/freezy/dmd-extensions/builds/46796240/job/go626t745c0vol57/artifacts

@coadaflorin Is there any update on the plan to support arm64e? We've been hitting this as well internally. It appears that `xcodebuild` is now using the arm64e arch as well,...

The key for me was to set the "Video Shaders" directory in Settings > Directory first. Navigating manually to the directory inside Quick Menu wouldn't show any selectable files.