Do it. The fewer “officially” supported compilers the better, it’s easier on everyone.
From: Michael Park<mailto:mp...@apache.org> Sent: Friday, July 28, 2017 5:38 PM To: dev<mailto:dev@mesos.apache.org> Subject: Dropping support for Apple Clang I'd like to drop support for Apple Clang. With the C++14 upgrade, we'll be requiring many distros to fetch a newer compiler. In most cases it only takes a few commands to get a newer compiler. This is also true of OS X, where clang-4.0 can be easily installed with `brew install llvm`. The current codebase does not compile with Apple Clang under C++14 mode. We could choose to investigate whether this is a Mesos bug or an Apple Clang bug, but after doing a brief investigation myself, I feel like it's not worth the effort. There are already cases where we need to install a new compiler on OS X due to Apple Clang releases based on clang-3.8 (MESOS-5745 <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FMESOS-5745&data=04%7C01%7Candschwa%40microsoft.com%7C91ce5c0c42f84ce851aa08d4d61a2ac9%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636368855258582598%7CUnknown%7CVW5rbm93bnx7IlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiT3RoZXIifQ%3D%3D%7C-1&sdata=ZzHd5rxJupR4Kr4fkoLgvj52DZu7ya3%2FT7D2SCwk1f4%3D&reserved=0>). Not that Apple Clang was "officially" supported anyway, but we have had minor workarounds (e.g., THREAD_LOCAL) to support it. Please let me know what you think! Thanks, MPark
