what does 'deprecated' mean with respect to "bare structure types"?

[james anderson]

On 11 Jun 2013, at 3:03 PM, Luís Oliveira wrote:

> On Tue, Jun 11, 2013 at 5:44 AM, james anderson <james.anderson at setf.de> wrote:
>> Still, the API argument stands.
>> 
>> which is? (a link to the pertinent point in the thread suffices.)
> 
> Given a clean start, the API wouldn't have a type that mixes value and
> reference semantics arbitrarily depending on the context since it's
> confusing. Deprecation is a reasonable path to cleanliness.

"arbitrarily depending on context" does not make sense. it is a contradiction in terms. there must be more to the argument than that.

if one takes that seriously, as it stands, one would have to deprecate something like (+ 1 2).

best regards, from berlin,