To repeat my statement from the PR:I would also prefer to avoid the generation of further functions, because I want to avoid the code bloat. I like the way of the current implementation, because it is following the way C++ does and will be understandable for every person which comes from C++.
Rather than raising the matter of scope again and again, we
should be thankful that a solution for this nasty problem is
accepted and could be merged. How scope and escape analysis could
do a better job is unclear and if you want to solve the problem
this way you will wait a very long time. So please let us
concentrate and discuss how we could solve this problem with auto
ref. :)
- Re: auto ref is on the ... Jonathan M Davis via Digitalmars-d
- Re: auto ref is on ... Daniel N via Digitalmars-d
- Re: auto ref i... Jonathan M Davis via Digitalmars-d
- Re: auto r... Daniel N via Digitalmars-d
- Re: auto ref is on the docket Andrei Alexandrescu via Digitalmars-d
- Re: auto ref is on the docket Jonathan M Davis via Digitalmars-d
- Re: auto ref is on the docket Andrei Alexandrescu via Digitalmars-d
- Re: auto ref is on the docket via Digitalmars-d
- Re: auto ref is on the docket Jonathan M Davis via Digitalmars-d
- Re: auto ref is on the dock... Manu via Digitalmars-d
- Re: auto ref is on the dock... Namespace via Digitalmars-d
- Re: auto ref is on the ... via Digitalmars-d
- Re: auto ref is on ... Namespace via Digitalmars-d
- Re: auto ref i... Temtaime via Digitalmars-d
- Re: auto r... Namespace via Digitalmars-d
- Re: auto r... kinke via Digitalmars-d
- Re: auto r... Timon Gehr via Digitalmars-d
- Re: auto r... kinke via Digitalmars-d
- Re: auto r... Timon Gehr via Digitalmars-d
- Re: auto r... kink via Digitalmars-d
- Re: auto ref is on ... Andrei Alexandrescu via Digitalmars-d
