Issue 2832: §[fpos.operations] strange requirement for P(i)

Title: §[fpos.operations] strange requirement for P(i)
Status: resolved
Section: [fpos.operations]
Submitter: Jens Maurer

Created on 2016-11-24.00:00:00 last changed 47 months ago

Messages

msg11291 (view)

Date: 2020-05-12.16:34:12

Resolved by

Rationale:

P0759R1.

msg10373 (view)

Date: 2020-05-15.00:00:00

[ 2020-05-12; Reflector discussions ]

Resolved by P0759R1.

msg10361 (view)

Date: 2019-03-15.00:00:00

[ 2019-03-17; Daniel comments ]

With the acceptance of P0759R1 at the Rapperswil 2018 meeting this issue should be closed as Resolved.

msg8808 (view)

Date: 2017-01-27.00:00:00

[ 2017-01-27 Telecon ]

Priority 3

msg8711 (view)

Date: 2016-11-24.00:00:00

This is from editorial issue #1031.

The first row in Table 112 "Position type requirements" talks about the expression P(i) and then has an assertion p == P(i). However, there are no constraints on p other than being of type P, so (on the face of it) this seems to require that operator== on P always returns true, which is non-sensical.

History
Date	User	Action	Args
2020-05-12 16:34:12	admin	set	messages: + msg11291
2019-03-22 17:53:09	admin	set	messages: + msg10373
2019-03-22 17:53:09	admin	set	status: new -> resolved
2019-03-17 18:39:01	admin	set	messages: + msg10361
2017-01-30 15:17:53	admin	set	messages: + msg8808
2016-11-24 00:00:00	admin	create