> On Mar 14, 2017, at 1:34 PM, Greg Parker via swift-dev <swift-dev@swift.org> > wrote: > > >> On Mar 14, 2017, at 12:43 PM, Joe Groff <jgr...@apple.com >> <mailto:jgr...@apple.com>> wrote: >> >> Hey Greg, what are the correct refcounting bits now to set in a global >> statically-emitted heap object that shouldn't ever be released? > > For now use the same thing that stack-allocated objects use. I forget what > the bit pattern is exactly. (I assume you are not in strictly read-only > memory and can tolerate writes to the refcount word. We don't yet have an > implementation for immortal read-only objects.)
Oh wait, you *don't* want to use what stack-allocated objects use. They get deinited without being deallocated, and I assume you want neither deinit nor dealloc. Let me work this out. -- Greg Parker gpar...@apple.com <mailto:gpar...@apple.com> Runtime Wrangler
_______________________________________________ swift-dev mailing list swift-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-dev
