-
Notifications
You must be signed in to change notification settings - Fork 9
P0009 : Address 2017-11 LEWG feedback to advance to LWG #48
Comments
TODO @hcedwar small group requested that the oral explanation that you and Christian gave in section 3.5.2 about "layout mapping of indices ... to codomain" be specified in detail Small group requested ability to index by template arguments, but large group showed no interest, |
@dsunder why did we remove the nullptr constructor again? Don’t we want this to be a nullable type? |
Feedback from LEWG on span and mdspan
From: David Hollman <[email protected]>
Reply-To: kokkos/array_ref <[email protected]>
Date: Sunday, February 11, 2018 at 8:22 AM
To: kokkos/array_ref <[email protected]>
Cc: "Edwards, Harold C" <[email protected]>, Mention <[email protected]>
Subject: [EXTERNAL] Re: [kokkos/array_ref] P0009 : Address 2017-11 LEWG feedback to advance to LWG (#48)
@dsunder<https://github.com/dsunder> why did we remove the nullptr constructor again? Don’t we want this to be a nullable type?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#48 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AHQObYWVcAizcD7VCgAHVWWuZvYmUs8Dks5tTwWngaJpZM4R-qHR>.
|
That was feedback on span, and it was pretty controversial. I don't think span intends to remove the nullptr constructor. I think it was made by someone who wasn't familiar with the importance of a |
From LEWG notes (included in #46): Poll to remove nullptr_t constructor: 4-5-3-0-0 |
I guess I was mixing it up with other discussion; sorry. |
Address 2017-11 LEWG feedback to advance to LWG.
The text was updated successfully, but these errors were encountered: