Tim Keith

`CHECK` and `DIE` are intended to be enabled in release builds. `std::assert` and `llvm_unreachable` are available for when you want them disabled in release builds. To change existing use of...

> Do we need _users_ to be able to use these for debugging? We want them enabled so that when users hit them they get a clear indication that it...

> > There's still discussion about how to represent runtime checks that we want to always be enabled, with or without NDEBUG. NDEBUG is a big hammer that I would...

> > I think I'm missing something here. You're not comfortable with flang containing runtime checks in release builds? Why? > > Runtime checks for invariants, yes - because it's...

Regarding `_en_US`: why would we want to allow non-English messages in the source? That would mean when the compiler is built normally it would produce messages in more than one...

The requirement we are currently meeting is that translatable strings are identified in the source. So it would not be hard to extract them, have them translated, and put the...

More pre-requisites: - complete the relicensing - update the f18 docs to describe the new process for making changes

> @tskeith I've added your suggestions above. Could you please clarify which docs need updating? I didn't see anything covering the mechanics on the flang side. Since it will be...

> @tskeith are you happy to be responsible for freezing submissions to the f18 repository, or finding someone to do this? I guess it amounts to removing commit access to...

Here's another example: `real :: a[1:*](4)`