Re: [swift-dev] Having 64-bit swift_retain/release ignore all negative pointer values

2016-10-16 Thread Dave Abrahams via swift-dev
on Thu Oct 13 2016, Joe Groff wrote: >> On Oct 13, 2016, at 1:18 PM, Greg Parker wrote: >> >> >>> On Oct 13, 2016, at 10:46 AM, John McCall via swift-dev >>> wrote: >>> > On Oct 13, 2016, at 9:04 AM, Joe Groff via swift-dev wrote: > On Mar 1, 2016, at 1:33 PM, Joe Gro

Re: [swift-dev] Validating ABI consistency between runtime C++ and standard library Swift code

2016-10-16 Thread Dave Abrahams via swift-dev
on Tue Oct 11 2016, Joe Groff wrote: > I just tracked down a bug due to C++ code in the Swift runtime code > trying to interface with standard library code written in Swift, but > getting the ABI slightly wrong and leading to some nasty > hard-to-reproduce heisenbugs. While I've narrowed down th

Re: [swift-dev] copy-on-write proposal

2016-10-16 Thread Dave Abrahams via swift-dev
on Tue Oct 11 2016, Erik Eckstein wrote: > This is a proposal for representing copy-on-write buffers in > SIL. Actually it’s still a draft for a proposal. It also heavily > depends on how we move forward with SIL ownership. > > :orphan: > > .. highlight:: sil > >

Re: [swift-dev] copy-on-write proposal

2016-10-16 Thread Dave Abrahams via swift-dev
on Thu Oct 13 2016, Joe Groff wrote: >> On Oct 11, 2016, at 4:48 PM, Erik Eckstein via swift-dev >> wrote: >> >> This is a proposal for representing copy-on-write buffers in >> SIL. Actually it’s still a draft for a proposal. It also heavily >> depends on how we move forward with SIL ownershi