Skip to content
This repository has been archived by the owner on Sep 18, 2024. It is now read-only.

P0900 Concerns - insufficiently vetted by Kokkos team #63

Open
hcedwar opened this issue Feb 11, 2018 · 7 comments
Open

P0900 Concerns - insufficiently vetted by Kokkos team #63

hcedwar opened this issue Feb 11, 2018 · 7 comments
Assignees

Comments

@hcedwar
Copy link
Contributor

hcedwar commented Feb 11, 2018

P0900 was generated quickly from some initial discussions. This proposal has not received sufficient vetting with the rest of the Kokkos / ISO-C++ team (@hcedwar, @crtrott, @dsunder, @mhoemmen). However, the 2018-03-Jacksonville pre-meeting deadline is too soon to allow sufficient vetting and this topic is too important to not submit a paper.

Decision: Revise abstract to note that this is initial exploration of this design. If the paper is taken up by LEWG at 2018-03-Jacksonville then the objective is to prompt discussion and collect perspectives of the available experts for a subsequent revision to (1) include more stakeholders and (2) make a concrete proposal.

@hcedwar hcedwar self-assigned this Feb 11, 2018
hcedwar added a commit that referenced this issue Feb 11, 2018
Add specific requests for LEWG straw polls on span proposal P0546.
@dhollman
Copy link
Contributor

@hcedwar have you sent it in?

@hcedwar
Copy link
Contributor Author

hcedwar commented Feb 12, 2018

In the next hour or so

@dhollman
Copy link
Contributor

What concerns? I was worried about this, which is why I only put my name on the paper so far.

@hcedwar
Copy link
Contributor Author

hcedwar commented Feb 12, 2018

It is not just an individual name on the paper, it is the organization you are representing. Sandia / the Kokkos project is sending you, you are not just representing yourself.

@dhollman
Copy link
Contributor

@hcedwar I know that; I didn't mean to imply otherwise.

@crtrott
Copy link
Member

crtrott commented Feb 12, 2018

OK I am pretty happy with the paper now after more understanding and a bit of discussion with David.

@mhoemmen
Copy link
Contributor

@hcedwar I did actually vet the paper (and proofread it too!). I think it makes a critical point about the risk of proliferating properties, and how we might mitigate that risk. Some of the details, like operator()'s suggested implementation, scare me a bit. Nevertheless, it's worth writing them down and discussing them, so that people realize the implementations. (Otherwise, "properties should be orthogonal" is just a platitude, like "don't kick puppies.")

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants