Re: new module 'noreturn'

[Paul Eggert]

I thought we had established that in some cases one should apply both 
_Noreturn and __attribute__ ((__noreturn__)) to the same declaration? I 
don't see that in this module.

Also, I hope we're not envisioning a lot of replacement of _Noreturn 
with _GL_NORETURN_FUNC in other modules. As I understand it, 
_GL_NORETURN_FUNC is needed only for functions that one wants to take 
addresses of, and to store these addresses in _GL_NORETURN_FUNCPTR 
variables. Most existing modules don't need to do this, and so can 
continue to use _Noreturn. This point should be made in the comments.