Issue 18209: 'Explicit alias' to clarify view copy semantics (vsiplxx-rtf)
Source:  (Mr. Brooks Moses, brooks.moses(at)dpdx.net)
Nature: Enhancement
Severity: Minor
Summary: In my previous issue, I stated with regards to clarifying the semantics
of a "View v(w)" statement: "Unfortunately this is not possible with the
alias case, but we can at least resolve it for the copy case.


This is not actually true.  We could define an alias() function (or
method) on a View which returns a unspecified type, and then a View
constructor that accepts that type as input and either creates an alias
to the precursor view or throws a compile error.  Thus, you could write


  View v(alias(w));


and know that, if it compiles, you are guaranteed to get a true alias.


Resolution: 
Revised Text: 
Actions taken:
October 23, 2012: received issue
Discussion: 

End of Annotations:=====
te: Tue, 23 Oct 2012 11:54:56 -0700
From: Brooks Moses <brooks_moses@mentor.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
To: <issues@omg.org>
Subject: VSIPL++ issue (#15 from me)
X-OriginalArrivalTime: 23 Oct 2012 18:54:56.0457 (UTC) FILETIME=[E4E83B90:01CDB14F]


Name:            Brooks Moses
Employer:        Mentor Graphics
mailFrom:        brooks_moses@mentor.com
Terms_Agreement: I agree
Specification:   VSIPL++
Section:         8 [view]
FormalNumber:    ptc/2012-07-27
Version:         1.2 - FTF Beta 1
Doc_Year:        2012
Doc_Month:       August
Doc_Day:         10
Page:            47-
Title:           'Explicit alias' to clarify view copy semantics
Nature:          Enhancement
Severity:        Minor
B1:              Report Issue


Description:


In my previous issue, I stated with regards to clarifying the semantics
of a "View v(w)" statement: "Unfortunately this is not possible with the
alias case, but we can at least resolve it for the copy case.


This is not actually true.  We could define an alias() function (or
method) on a View which returns a unspecified type, and then a View
constructor that accepts that type as input and either creates an alias
to the precursor view or throws a compile error.  Thus, you could write


  View v(alias(w));


and know that, if it compiles, you are guaranteed to get a true alias.

- Brooks