Re: [swift-users] Need some help understanding test behavior.

This sounds like a question for the swift-dev list, directed toward whomever has been working on linux/powerpc support... > On Dec 14, 2017, at 3:25 AM, Atul Sowani via swift-users > wrote: > > Hi, > > I am trying to understand behavior of Swift test case

Re: [swift-users] Tuple of two or more instances to withExtendedLifetime

Yes, withExtendedLifetime is a generic API that guarantees the lifetime of any non-trivial value. i.e. if the tuple contains a reference, the lifetime of that reference will be extended. That said, there is a theoretical bug in the optimizer that you will be much more likely to hit in practice

Re: [swift-users] Why does the withUnsafeMutableBufferPointer closure take an inout parameter?

> On Oct 12, 2017, at 3:52 AM, Geordie Jay via swift-users > wrote: > > > Guillaume Lessard via swift-users > schrieb am Mi. 11. Okt. 2017 um 23:49: > A lot of the MutableCollection implementation is in protocol

Re: [swift-users] Memory Address of value types and reference types

> On Sep 12, 2017, at 9:55 AM, somu subscribe via swift-users > wrote: > > Hi Quinn, > > Thanks for the reply, > > It is an iOS Swift project (uses Foundation, UIKit, CloudKit and other native > frameworks) in which I would like to check the memory address for

Re: [swift-users] Law of Exclusivity runtime false positive?

> On Jul 30, 2017, at 5:11 AM, David Hart via swift-users > wrote: > >> >> On 28 Jul 2017, at 18:55, Joe Groff > > wrote: >> >>> >>> On Jul 28, 2017, at 12:06 AM, David Hart via swift-users >>>

Re: [swift-users] Passing Data to a f(void *) function

> On Jun 30, 2017, at 9:14 AM, Joe Groff via swift-users > wrote: > > >> On Jun 30, 2017, at 7:40 AM, Martin R via swift-users >> wrote: >> >> I have a C function >> >> void myfunc(const void *ptr); >> >> which is imported to Swift as >>

Re: [swift-users] Ugliness bridging Swift String to char *

> On Mar 1, 2017, at 7:08 PM, Kenny Leung via swift-users > wrote: > > Hi Jordan. > > Thanks for the lengthy answer. > >> On Mar 1, 2017, at 6:21 PM, Jordan Rose > > wrote: >> >> Hey, Kenny. The const vs non-const

Re: [swift-users] unsafeBitCast to Unimplemented Class

> On Feb 6, 2017, at 8:51 PM, Dave Abrahams wrote: > > > on Mon Feb 06 2017, Andrew Trick wrote: > >> Is a missing declaration a use case that needs to be supported? > > I couldn't say. > >> Wouldn’t it be more proper to use selector based dispatch in those >> cases? >

Re: [swift-users] unsafeBitCast to Unimplemented Class

> On Feb 5, 2017, at 9:01 AM, Dave Abrahams via swift-users > wrote: > > > on Sat Feb 04 2017, Saagar Jha > wrote: > >> Thanks–your not only did you method work, it had the side effect of >> obviating the need for a Bridging Header. >

Re: [swift-users] isKnownUniquelyReferenced really a mutating function?

> On Jan 25, 2017, at 10:53 AM, Edward Connell via swift-users > wrote: > > I am implementing a custom Array type for a distributed memory system. > > I have a DataView struct which represents the array to the user as a value > type, and a backing store class object

Re: [swift-users] How much memory does withMemoryRebound bind

> On Dec 29, 2016, at 2:03 PM, Guillaume Lessard via swift-users > wrote: > > Hi Etan, > > `withMemoryRebound` does not copy memory. > The proposal for UnsafeRawPointer contains information about the memory model > (as related to pointers): >

Re: [swift-users] Atomics and Memory Fences in Swift

> On Nov 30, 2016, at 5:40 AM, Anders Ha via swift-users > wrote: > > Hi guys > > I have recently started adopting lock-free atomics with memory fences, but it > seems Swift at this moment does not have any native instruments. > > Then I read a thread in the Apple

Re: [swift-users] What is "binding" memory?

> On Nov 4, 2016, at 12:16 AM, Rien wrote: > > Thanks Any, most informative. > > So the pointer “gateway’s” are in fact ephemeral. That is good for > performance. > > As to the low level interfaces, are you aware of any effort that addresses > the POSIX socket

Re: [swift-users] What is "binding" memory?

> On Nov 3, 2016, at 7:41 AM, Rien via swift-users > wrote: > >> On 03 Nov 2016, at 15:16, Manfred Schubert via swift-users >> > wrote: >> >> >>> Am 02.11.2016 um 18:37 schrieb Rien >>

Re: [swift-users] What is "binding" memory?

> On Nov 3, 2016, at 7:16 AM, Manfred Schubert via swift-users > wrote: > > >> Am 02.11.2016 um 18:37 schrieb Rien : >> var rawPtr = UnsafeMutableRawPointer.allocate(bytes: 2, alignedTo: 0) var widePtr =

Re: [swift-users] What is "binding" memory?

> On Nov 2, 2016, at 10:37 AM, Rien via swift-users > wrote: > >>> var rawPtr = UnsafeMutableRawPointer.allocate(bytes: 2, alignedTo: 0) >>> >>> var widePtr = rawPtr.bindMemory(to: Int16.self, capacity: 1) >>> >>> widePtr.pointee = 32 >>> >>> var narrowPtr =

Re: [swift-users] What is "binding" memory?

> On Nov 2, 2016, at 10:32 AM, Manfred Schubert via swift-users > wrote: > > Am 01.11.2016 um 21:43 schrieb Michael Ilseman : >> >> This is more so a semantic distinction rather than some kind of physical >> operation. The memory is not altered, but

Re: [swift-users] What is "binding" memory?

> On Nov 2, 2016, at 10:07 AM, Manfred Schubert via swift-users > wrote: > > Am 01.11.2016 um 21:40 schrieb Andrew Trick : >> >> I’m not sure I like the “prepares the memory” language myself. Binding >> memory communicates to the compiler that the

Re: [swift-users] What is "binding" memory?

> On Nov 2, 2016, at 3:50 PM, Dave Abrahams wrote: > >> The original poster seemed to have the impression that the operation >> of binding memory itself might affect program state, > > Formally speaking, it does! Oh boy. I keep failing at this. How does one formally

Re: [swift-users] What is "binding" memory?

> On Nov 1, 2016, at 11:55 AM, Manfred Schubert via swift-users > wrote: > > The "UnsafeRawPointer Migration" guide talks about "binding memory to a type“ > as if that was a well known term. I have never heard of it yet though, and > googling it returns no relevant

Re: [swift-users] How to malloc in Swift 3

> On Sep 23, 2016, at 2:23 PM, Joe Groff wrote: > > >> On Sep 23, 2016, at 2:20 PM, Jens Persson wrote: >> >> What is the difference between: >> ptr.storeBytes(of: x, toByteOffset: offset, as: type(of: x)) >> ptr.advanced(by:

Re: [swift-users] Function to unsafe pointer and back

> On Sep 2, 2016, at 9:49 AM, Jordan Rose wrote: > > (One place we are still weak is in converting between C function references > and UnsafeRawPointer—there’s no dedicated API to do this. I’m not sure we > have a recommendation in the rare cases when this is necessary.

Re: [swift-users] Function to unsafe pointer and back

> On Sep 1, 2016, at 12:37 PM, Lou Zell via swift-users > wrote: > > As to your real question, what’s your high-level goal? Swift doesn’t really > do pointers to functions [1] but it does provide lots of other excellent > ‘treat code as data’ features. If you can

Re: [swift-users] Data(bytesNoCopy:count:deallocator)

> On Aug 23, 2016, at 8:40 AM, Stéphane Lizeray via swift-users > wrote: > > Hello, > > I create an UsafeMutableRawPointer using the allocate method. > > Later on I want to create a Data struct from this pointer using the > bytesNoCopy initializer. Which deallocator

Re: [swift-users] Pointer conversions between different sockaddr types

> On Aug 20, 2016, at 4:02 AM, Michael Ferenduros via swift-users > wrote: > >> >> On 20 Aug 2016, at 07:25, Andrew Trick > > wrote: >> >>> >>> On Aug 19, 2016, at 4:49 PM, Michael Ferenduros via swift-users >>>

Re: [swift-users] Pointer conversions between different sockaddr types

> On Aug 19, 2016, at 4:49 PM, Michael Ferenduros via swift-users > wrote: > > >>> On Aug 18, 2016, at 12:28 AM, Quinn The Eskimo! via swift-users >>> wrote: >>> >>> >>> On 17 Aug 2016, at 18:55, Martin R via swift-users >> swift.org> wrote: >>> - Are both

Re: [swift-users] Pointer conversions between different sockaddr types

> On Aug 18, 2016, at 12:28 AM, Quinn The Eskimo! via swift-users > wrote: > > > On 17 Aug 2016, at 18:55, Martin R via swift-users > wrote: > >> - Are both solutions correct, should one be preferred, or are both wrong? > > Your

Re: [swift-users] NSData and UnsafePointer

> On Jul 16, 2016, at 5:28 AM, J.E. Schotsman via swift-users > wrote: > > A mysterious bug has got me thinking about using UnsafePointer with > NSData (Swift 2). > > Is this safe: > > let data:NSData = … > let dataStart = UnsafePointer(data:NSDAta.bytes) > >

Re: [swift-users] Unsafe(Mutable)Pointer (suc)predecessor and advancedBy functions

> On May 26, 2016, at 9:59 AM, Adrian Zubarev via swift-users > wrote: > > I’ve got one more questions about Unsafe(Mutable)Pointer. I know that I’m > able to access memory that might not belong to me. > > My question is: > > Can I trust these functions that they