(In reply to comment #23) > This is a feature, not a bug. Features do not block releases. > > It's a feature because it's new behaviour to be added to Clang, not a > regression in an old behaviour. That GCC designed and implemented this and > that Linux distributions took that and ran with it is irritating, but does > not make it a release blocker. > > Implementing a new feature is not a one line fix, it's not something that > can be merged to the release branch quickly - it needs design (especially in > this case!) and soak testing. > > It's nigh-on impossible for this to be done for the release, and therefore > it makes no sense to have it block the release IMHO.
James is right; we cannot block the release on the development of this feature. Also, if you'd like to express your support for the development of this feature to the Clang/LLVM community, you'll need to do it on llvm-dev /cfe-dev, not here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1488254 Title: clang++ no longer ABI-compatible with g++ To manage notifications about this bug go to: https://bugs.launchpad.net/llvm/+bug/1488254/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
