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

2017-05-03 Thread Guillaume Lessard via swift-users
It works now, but it's not correct. I wish there were a correct way available. Guillaume Lessard > On May 3, 2017, at 21:30, Colin Barrett via swift-users > wrote: > > I haven't used this in production, but this repository looks pretty > promising. It's more or less just wrapping up the clang

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

2017-05-03 Thread Colin Barrett via swift-users
I haven't used this in production, but this repository looks pretty promising. It's more or less just wrapping up the clang atomic intrinsics into a Swift package. https://github.com/glessard/swift-atomics -Colin On Mon, May 1, 2017 at 12:43 PM Joe Groff via swift-users < swift-users@swift.org>

Re: [swift-users] stack trace of Swift executable

2017-05-03 Thread Alex Blewitt via swift-users
Greg, This occurs when compiled with swiftc -g as well. In fact, I think 'swift build', when run by default, will compile with swiftc -g. It's only when you run 'swift build --configuration release' that it will compile without it. $ swiftc --version Apple Swift version 3.1 (swift-3.1.1-RELEASE