February 2020 Fortran Meeting

[certik]

Fortran Committee Meeting February 24 - 28, 2020, Las Vegas, NV, USA

People

1. Dan Nagle (NCAR)
2. Steven Lionel (WG5) @sblionel
3. Jon Steidel (Intel) @JonSteidel
4. Bill Long (Cray / HPE) @longb
5. Peter Klausler (Nvidia) @klausler
6. Reuben Budiardja (ORNL) @reubendb
7. Daniel Chen (IBM) @DanielCChen
8. Brad Richardson (Structural Integrity) @everythingfunctional
9. Brian Friesen (LBNL) @bcfriesen
10. Erhard Ploedereder (WG23)
11. Srinath Vadlamani (ARM) @srinathv
12. Tom Clune (NASA) @tclune
13. Gary Klimowicz (Nvidia) @gklimowicz
14. Rich Bleikamp (AMD) @rbleikamp
15. Van Sneider (JPL)
16. Zach Jibben (LANL) @zjibben
17. Malcolm Cohen (NAG)
18. Stephen Michell (WG23)
19. Ondřej Čertík (LANL) @certik
20. Bob Corbett
21. Vipul Parekh
22. Damian Rouson (Sourcery, Inc.) @rouson
23. Magne Haveraaen (University of Bergen)

Proposals Discussed at Plenary

Tuesday 2/25

• Allow setting default value for optional dummy argument #22: Default values of optional arguments (https://j3-fortran.org/doc/year/20/20-107.txt)

Wednesday 2/26

• Rank-agnostic array element and section denotation #157: Rank-agnostic array element and section denotation (https://j3-fortran.org/doc/year/20/20-113.txt, https://j3-fortran.org/doc/year/20/20-115.txt)
• US16 TYPEOF and CLASSOF #158: TYPEOF and CLASSOF (https://j3-fortran.org/doc/year/20/20-114.txt)
• Namespace for modules #1: Namespace for modules (https://j3-fortran.org/doc/year/20/20-108.txt)
• Interpretation: FORM TEAM and failed images (https://j3-fortran.org/doc/year/20/20-102r1.txt)
• Interpretation: Collective subroutines and STAT= (https://j3-fortran.org/doc/year/20/20-104r1.txt)

Thursday 2/27

• Interpretation: events that cause variables to become undefined (https://j3-fortran.org/doc/year/20/20-119.txt)
• Edits for SIMPLE procedures (https://j3-fortran.org/doc/year/20/20-116.txt)
• BFLOAT16 (https://j3-fortran.org/doc/year/20/20-118.txt)
• Finalization order for complex objects: official interpretation needed? #146: Interpretation: allocatable component finalization (https://j3-fortran.org/doc/year/20/20-117.txt)

Friday 2/28

• Rank-agnostic array element and section denotation #157: Rank-agnostic syntax (https://j3-fortran.org/doc/year/20/20-120.txt). Passed unanimously with minor changes.
• Protected Components #156: Protected components (https://j3-fortran.org/doc/year/20/20-121.txt). Withdrawn to address conflicting interests.
• Auto-allocating processor messages #160: Edits for auto-allocate characters (https://j3-fortran.org/doc/year/20/20-122.txt). Passed unanimously with minor changes.
• Edits for procedure pointer association (https://j3-fortran.org/doc/year/20/20-123.txt). Passed unanimously.
• Rank-agnostic array element and section denotation #157: Edits for rank-agnostic bounds (https://j3-fortran.org/doc/year/20/20-124.txt). Withdrawn because some edits were missing and need to be added. There were concerns about fitting into the framework of generics later on.
• Rank-agnostic array element and section denotation #157: Edits for rank-agnostic array element and section denotation (https://j3-fortran.org/doc/year/20/20-125.txt). Failed (5 v 7). Missing edits, and disagreement on types vs rank-1 integers, the options need to be explored more.
• Rank-agnostic array element and section denotation #157: Edits for rank-agnostic allocation and pointer assignment (https://j3-fortran.org/doc/year/20/20-126.txt). Passed unanimously with minor changes.
• Interpretation: Public namelist and private variable (https://j3-fortran.org/doc/year/20/20-127.txt). Straw vote (0 yes, 8 no, 9 undecided). Passed unanimously with "no" alternative.
• Interpretation F18/015 (https://j3-fortran.org/doc/year/20/20-105.txt). Passed unanimously.

Future Plan

This was on the plan but we didn't get to it:

• Allowing "const" on pointed to data #5: US 27 POINTER dummy arguments, INTENT, and target modification (https://j3-fortran.org/doc/year/18/18-144r1.txt)
• Short-circuiting logical expressions #19: Short-circuiting

[marshallward]

Big thanks to @certik and @zjibben for preparing this report and keeping us connected with the subcommittee discussions.

This greater transparency gives us more confidence to commit to the language in our own work, and is a great continuation of the work done by @sblionel and others in J3.

I hope that the other committee members will also contribute to the discussions here and help all of us better understand the contours of the language and its evolution.