@FortranFan submitted this at #105, I moved it to a separate issue here, so that we do not derail a discussion at #105.
Sorry for going off-topic but to me this proposal looks rather straightforward and without serious side effects and any concerns or issues raised with something like this are going to be an overreach and can be heavily debated whether they're technical at all.
So the question is why does this have to Fortran 202Y whose timeline is likely in the year 2028 at the earliest?
That is, other than perhaps a project management type of decision by WG5 on the work-list toward Fortran 202X? But who should WG5 represent other than the "many users" who "have asked for a way to" need this? And since many other features of interest to said users have been deferred or rejected by WG5 for Fortran 202X anyway, why not carve out an avenue to add many other smallish features to Fortran 202X which will at least add some heft to what appears otherwise a rather dull revision considering the five years devoted to its development?
Suggestions such as these appear to me to be in the Just do it! category and the standards revision process must have a pathway to introduce any number of them into the language as soon as the work is completed like in an online development platform.
certik, epagone and beddalumia
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4