Issaquah Meeting Plan

Atomic Accessor: P2689

• introduce atomic_ref_relaxed/acq_rel/seq_cst (Christian or Nevin first draft)
• introduce atomic_accessor_relaxed/acq_rel/seq_cst (Christian or Nevin first draft)
• implement this (Damien - start with implementation just in desul for ourselves)

PaddedLayout: P2642

• switch to pandoc (Mark meeting with Christian for pandoc, then Mark)
• fix wording (Together meeting)
• prepare comparative wording review (i.e. side-by-side layout_left_padded vs layout_left)

mdarray: P1684

• still discussion on constructors - maybe want to ask mailing list

subdmspan: P2630

• explore customization point options (Christian first draft)
  • P2279
  • need code examples of pure ADL vs tag-invoke vs CPOs
  • talk to Zache Laine

linalg: P1673

• split into: packed_layouts (lowest priority), view adaptor functions, actual math
  • make new papers already pandoc
• P1673 actual math
  • We can just write Effects: Computes the matrix vector product y=Ax.
  • Front matter syntactic requirements: require linear algebra element types to be well formed for possible :
    • a linear algebra element type for any of these functions are:
      • return types of mdspan [] operators
      • mdspan::element_type, mdspan::value_type
      • decltype(T0+T1), decltype(T0-T1) where T0 and T1 are linear algebra element types
      • distinguish assignable and non-assignable LA element types
    • define all the wellformed binary operation (+ += = - ...)
    • special case only division for the functions which need that
    • maybe do this as concepts

Start by reviewing the meeting-plan sections for P2689, P2642, P1684, P2630, and P1673, including the referenced P2279 and P1673 subdivisions. Check the listed pandoc, wording, customization-point, constructor, and linear-algebra requirements; the issue does not define one bounded deliverable or a single completion test.