https://issues.dlang.org/show_bug.cgi?id=17289
Vladimir Panteleev <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|regression |major --- Comment #15 from Vladimir Panteleev <[email protected]> --- (In reply to Zach the Mystic from comment #13) > If you're running a business, you wouldn't tell your customers, "Our > supplier crashed their truck, so we're not required to serve you." Bad analogy. It is your choice to use Apple products, your choice to update Xcode, and your choice to (instead of using a workaround) attempt to escalate the issue, here, on D's bugtracker, even though the breaking change was in Xcode, not D. > A good business focuses on the customer. Well... would you like a refund? Luckily for us, D is not a business, it's an open-source project. > and it's D users who are hurting. 1. Only Apple users. 2. "Hurting"? Isn't it just warnings? > and the fix should be patched to the main website ASAP. We are not going to make an exception for our release process for a LINKER WARNING. All in all, I definitely don't see any reason to treat this issue with the urgency you demand, and I don't think the tone of your communication is of any help to anyone. There are multiple workarounds available at your disposal: - Build D from git - Use a nightly version of D (https://nightlies.dlang.org/dmd-nightly/) - Filter out the linker warnings locally - Downgrade Xcode - Use a different operating system Considering the fix was already merged, please make use of one of the workarounds above and stop exaggerating the problem. --
