Tail pad optimization, cache friendlyness and C++ interrop

[H. S. Teoh via Digitalmars-d]

On Wed, Jun 18, 2014 at 04:39:27PM +0000, Dicebot via Digitalmars-d wrote:
> On Wednesday, 18 June 2014 at 07:05:13 UTC, deadalnix wrote:
> >On Wednesday, 18 June 2014 at 07:02:43 UTC, Walter Bright wrote:
> >>On 6/17/2014 11:50 PM, deadalnix wrote:
> >>>and the fact that @safe is defined backward (ie by listing what is not
> >>>allowed and
> >>>adding to the list when new holes are discovered
> >>
> >>https://issues.dlang.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&keywords=safe%2C%20&keywords_type=allwords&list_id=41168&query_format=advanced
> >>
> >>Currently, there are zero bugzilla issues tagged with 'safe'. Please
> >>file bugzilla issues for which ones are discovered and tag them!
> >
> >I don't even know what to answer to that. We are clearly talking past
> >each other here, and I have no idea how to convey the message in a
> >better way.
> 
> Create a bugzilla issue to make everything unsafe and list there
> constructs you think can be defined as safe :)

Everyone talks about it, but nobody does anything about it, so here goes
nothing:

	https://issues.dlang.org/show_bug.cgi?id=12941

Obviously, I have no idea what should go in that list, so everyone who
cares about this issue, please chime in. Thanks!

P.S. I've also tagged a whole bunch of issues with 'safe'. It's just
based on a quick skim over all issues that turned up when I searched for
'safe', so I may have mistagged some, and missed others, but this is
just to get the ball rolling. Please fix wrong/missing tags if you find
them. :)


T

-- 
I'm still trying to find a pun for "punishment"...