I love how using cached binaries speeds up Xcode UI and building. I don’t love not having access to the source though. It’s a pain to have to switch between cached and uncached whenever I want to view or step into the source of a cached binary.
I think it would be great to have a third option: include the module as source (so this wouldn’t improve Xcode UI as the full project is loaded), but have its build step be to just provide the cached binary (so we keep improved build times). Just being able to browse/search the code would be a huge boon. Even better would be if the debugger somehow knew the code corresponds to the cached binary at runtime for stepping into it.
It’s a single CLI command, but yeah, if you do have to do it often, I can understand it can get somewhat annoying.
This should definitely be feasible without a ton of work involved. But I’m not sure how useful this alone would be to be honest and whether it would be somewhat confusing to developers that there’s source code that’s actually not used when building.
I am honestly not sure if this is possible. Even if it was, it could also cause confusion that editing the source file wouldn’t actually get propagated into the build.
True. I don’t have real world data on this yet, but I’m imagining a future where devs are working on a focused subset of our project. I’m thinking it might be common for them to want to go into the source of one of our internal modules that is outside of the current focus.
I can bring this up again if it becomes more of an actuality.