Date: Fri, 31 May 2024 12:12:00 -0300
On Friday 31 May 2024 09:31:29 GMT-3 Frederick Virchanza Gotham via Std-
Proposals wrote:
> Well it wouldn't be Friday if I didn't write a new paper so here goes:
>
> http://www.virjacode.com/papers/prvalue_params.htm
A prvalue is a special type of rvalue. What you're saying is that rvalue-ref
functions can only accept xvalues but not prvalues, though that's patently
false.
void f(int &&);
void f()
{
f(3);
}
3 is a prvalue and is accepted.
Given that your introduction section contains such a blatant absurdity, either
your paper is entirely wrong or you're using wrong terms to mean what you want
to mean. I didn't read the rest.
I did notice you're still using std::mutex in your examples, though. STOP
DOING THAT. Anyone reading the paper will again go into the discussion of how
returning a mutex is pointless. Find another, real type that is immovable but
makes sense to return.
Proposals wrote:
> Well it wouldn't be Friday if I didn't write a new paper so here goes:
>
> http://www.virjacode.com/papers/prvalue_params.htm
A prvalue is a special type of rvalue. What you're saying is that rvalue-ref
functions can only accept xvalues but not prvalues, though that's patently
false.
void f(int &&);
void f()
{
f(3);
}
3 is a prvalue and is accepted.
Given that your introduction section contains such a blatant absurdity, either
your paper is entirely wrong or you're using wrong terms to mean what you want
to mean. I didn't read the rest.
I did notice you're still using std::mutex in your examples, though. STOP
DOING THAT. Anyone reading the paper will again go into the discussion of how
returning a mutex is pointless. Find another, real type that is immovable but
makes sense to return.
-- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Principal Engineer - Intel DCAI Fleet Engineering and Quality
Received on 2024-05-31 15:12:08