BitArray new design - slice problems

Era Scarecrow rtcvb32 at yahoo.com
Thu Jan 17 13:49:15 PST 2013


On Thursday, 17 January 2013 at 19:36:34 UTC, Dmitry Olshansky 
wrote:
> I'm thinking that a opSlice of stack-allocated must be @system 
> and a heap allocated can be @safe.

  That's just a small part of the problem. With the new design, 
90% of it can be safe; Just the actual slice buffer when you 
request it (with Fixed storage) would be @system, and slices 
(having a pointer). But @safe code can't call @system code which 
means that the current design (convert to slices before 
operations) it all has to all be @system.

  Guess once it's debugged the entire thing can be @trusted and 
only certain things can be marked @system instead.


More information about the Digitalmars-d-learn mailing list