220 13346 article Path: news.gmane.org!not-for-mail From: gmisocpp@gmail.com Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: Re: proposal: deprecate failure to return (without annotation) Date: Mon, 29 Sep 2014 16:54:05 -0700 (PDT) Lines: 88 Approved: news@gmane.org Message-ID: References: <2106187.KAVOBzdsgo@tjmaciei-mobl4> <7890243.H6e3ul2NkU@tjmaciei-mobl4> Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1134_1715752589.1412034845469" X-Trace: ger.gmane.org 1412034857 31902 80.91.229.3 (29 Sep 2014 23:54:17 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 29 Sep 2014 23:54:17 +0000 (UTC) Cc: gmisocpp@gmail.com To: std-proposals@isocpp.org Original-X-From: std-proposals+bncBCM3TRNUXUDBBH7CU6QQKGQEXWQVDDY@isocpp.org Tue Sep 30 01:54:10 2014 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-ob0-f200.google.com ([209.85.214.200]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1XYklc-0001WU-VD for gclcip-std-proposals@m.gmane.org; Tue, 30 Sep 2014 01:54:09 +0200 Original-Received: by mail-ob0-f200.google.com with SMTP id m8sf113387157obr.7 for ; Mon, 29 Sep 2014 16:54:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:message-id:in-reply-to:references:subject :mime-version:x-original-sender:reply-to:precedence:mailing-list :list-id:list-post:list-help:list-archive:list-subscribe :list-unsubscribe:content-type; bh=hq70LuPZo5iMB4Kgn99WXJM5+ayBpLwSvNxu0CGxOMU=; b=xuF1O7QZAai5Zcx3pgsY2Ef0WvU89T57TD0xSZB2WNsve/He3UKv+AECwB+JkWcxCw cjM3TTFICrHMif5ddOx1dpoovhtFHcJR+rwDZkjr95sOxsRF11wCUhM1sVw29Uz1kyJa 86o8hicgG4e23AsIonv+xt9L/m2+ANspE6MnHJXBxRathIobjUR/zUOFZfGRUgo5RRjK YggvrcYrlxx/JGIpFE+KMYeDZfvFQ9xOGDXsO7xCV/z3wXB0rvAZJQeRpSrB2oTlZLZb 35FvMu10mollyiI7slkTHBBG1lKHauEJJ4Ny++P78HkIzIN+ox4Ovp7+0GOXpR6EKSKX wKEw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:message-id:in-reply-to :references:subject:mime-version:x-original-sender:reply-to :precedence:mailing-list:list-id:list-post:list-help:list-archive :list-subscribe:list-unsubscribe:content-type; bh=hq70LuPZo5iMB4Kgn99WXJM5+ayBpLwSvNxu0CGxOMU=; b=Stxz0V75pCfHgjTe+SSkKgysMHN/yZ/V1hlH8TP9sLTKNNUXYCZLIj4Crl/MNB9+Of FJY0kcpxee0Nzn8AGQvNMXxkAhADp5Q7sAQHl7FUe8dIp0zP/AdUJNrBs1cu/DYRyDuE NqzNQT2tuJI7ew4ioH/uIVYibiJ2SFnTZRZMBMTm8A/CV5UuYdCrWcLuwmJmVitdAQUp xGVchkiiH4DeTeZGcJHy8K/cpvfr+FyRGrBOhLV6BQ+pyTAMXGjSz7V1i5q4Glla4fgK E6+V1WaeMEYnWJzr2BV951y92Xg8u+RleUovND1R3XLHcN9yNMeU4f/AAYT5hyFtp48e 0Rvg== X-Gm-Message-State: ALoCoQkL1RthoyGItB83lETjJkqSpQpe5eDTJ2HJeYgmd+PREXlv7bfs8rMDfKauscqFBqYZ0QDF X-Received: by 10.43.71.81 with SMTP id yj17mr38377902icb.26.1412034847856; Mon, 29 Sep 2014 16:54:07 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.50.222.38 with SMTP id qj6ls2625102igc.9.canary; Mon, 29 Sep 2014 16:54:07 -0700 (PDT) X-Received: by 10.50.41.103 with SMTP id e7mr32063igl.8.1412034847032; Mon, 29 Sep 2014 16:54:07 -0700 (PDT) In-Reply-To: X-Original-Sender: gmisocpp@gmail.com Precedence: list Mailing-list: list std-proposals@isocpp.org; contact std-proposals+owners@isocpp.org List-ID: X-Google-Group-Id: 399137483710 List-Post: , List-Help: , List-Archive: List-Subscribe: , List-Unsubscribe: , Xref: news.gmane.org gmane.comp.lang.c++.isocpp.proposals:13346 Archived-At: ------=_Part_1134_1715752589.1412034845469 Content-Type: text/plain; charset=UTF-8 On Tuesday, September 30, 2014 12:41:21 PM UTC+13, Matheus Izvekov wrote: > > On Monday, September 29, 2014 8:28:04 PM UTC-3, gmis...@gmail.com wrote: >> >> enum E { a, b, c }; >> int f(E e) { >> // switch cases must cover all enum values or trigger error/warning. >> switch (e) [[switch_on_all_enum_values]] (E) { >> case a: return 1; >> case b: return 2; >> case c: return 3; >> } >> > > There is something wrong with that example, the (E) seems completely out > of place with the language, I am not sure if that was intentional. > > But otherwise, this seems like an acceptable use of attributes according > to existing guidelines. > It does not introduce any semantic changes and the attribute can be safely > ignored. > Yes, sorry, the (E) was a typo, perhaps because I was considering at the time if the type name needed to appear in the attribute. I decided it didn't but left text relating to it in by mistake. It might appear in my other post too as I cut and pasted. Thanks for pointing that out. -- --- You received this message because you are subscribed to the Google Groups "ISO C++ Standard - Future Proposals" group. To unsubscribe from this group and stop receiving emails from it, send an email to std-proposals+unsubscribe@isocpp.org. To post to this group, send email to std-proposals@isocpp.org. Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposals/. ------=_Part_1134_1715752589.1412034845469 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Tuesday, September 30, 2014 12:41:21 PM UTC+13,= Matheus Izvekov wrote:
On Mon= day, September 29, 2014 8:28:04 PM UTC-3, gmis...@gmail.com wrote:
enum E { a, b, = c };
int f(E e) {
  // switch cases must cover all enum values o= r trigger error/warning.
  switch (e) [[switch_on_all_enum_values]]= (E) {
  case a: return 1;
  case b: return 2;
  ca= se c: return 3;
  }

There is somet= hing wrong with that example, the (E) seems completely out of place with th= e language, I am not sure if that was intentional.

But otherwise, th= is seems like an acceptable use of attributes according to existing guideli= nes.
It does not introduce any semantic changes and the attribute can be= safely ignored.

Yes, sorry= , the (E) was a typo, perhaps because I was considering at the time if the = type name needed to appear in the attribute.
I decided it didn't = but left text relating to it in by mistake. It might appear in my othe= r post too as I cut and pasted.
Thanks for pointing that out.


--

---
You received this message because you are subscribed to the Google Groups &= quot;ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to std-proposa= ls+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposals/<= /a>.
------=_Part_1134_1715752589.1412034845469-- .