Javascript bytecode

[Jonathan M Davis]

On Tuesday, December 18, 2012 17:57:50 Brad Roberts wrote:
> On Tue, 18 Dec 2012, Andrei Alexandrescu wrote:
> > On 12/18/12 7:29 PM, H. S. Teoh wrote:
> > > Which right now suffers from some silly things like writefln not being
> > > able to be made @safe, just because some obscure formatting parameter is
> > > un at safe. Which is exactly how @safe was designed, of course. Except
> > > that it makes SafeD ... a bit of a letdown, shall we say? - when it
> > > comes to practical real-world applications.
> > > 
> > > (And just to be clear, I'm all for SafeD, but it does still have a ways
> > > to go.)
> > 
> > Yes, there are several bugs related to SafeD.
> > 
> > Andrei
> 
> Are the remaining issues at the compiler, runtime, or phobos levels (or
> what combination of the three)? Are the bugs filed?

Quite a few are, but it wouldn't surprise me at all if there are quite a few 
which aren't. For instance, AFAIK, no one ever brought up the issue of slicing 
static arrays being unsafe until just a couple of months ago:

http://d.puremagic.com/issues/show_bug.cgi?id=8838

Such operations should be @system but are currently considered @safe. Who 
knows how many others we've missed beyond what's currently in bugzilla.

- Jonathan M Davis