[swift-users] Cannot pass immutable value as inout argument

Is it not possible for Swift to treat C API const pointers as something that can take let arguments? LGS_EXPORT bool lgs_notify(struct lgs_context_t* ctx, const lgs_notify_params_t* params); . . . let p = lgs_notify_params_t(...) lgs_notify(self.ctx, ) ^Cannot pass

Re: [swift-users] .apinotesc file placement?

errors illustrates the problem: BLK360API.swift:664:9: Type 'lgs_status_t' has no member 'aborted' BLK360Request.swift:657:9: 'lgs_status_aborted' has been renamed to 'lgs_status_t.aborted' > On Nov 29, 2017, at 16:05 , Rick Mann via swift-users <swift-users@swift.org> > wrote:

Re: [swift-users] Making a copy of an UnsafePointer

> On Nov 15, 2017, at 00:48 , Quinn The Eskimo! via swift-users > <swift-users@swift.org> wrote: > > > On 15 Nov 2017, at 04:16, Rick Mann via swift-users <swift-users@swift.org> > wrote: > >> Is UnsafeMutablePointer<> not memory managed? >

[swift-users] Making a copy of an UnsafePointer

My code gets some data from an OpenCV cv::Mat object, and passes it to some Swift code that takes it via an UnsafePointer parameter. This works fine until I want to make the call asynchronous (using a DispatchQueue), I think because the underlying cv::Mat gets deallocated by the caller before

Re: [swift-users] Passing variadic C args through?

nch of arguments >>> in an Array, and then passing that array straight on as a single argument >>> itself, which means it gets passed as either an NSArray or a pointer (not >>> sure which). Use 'init(format:arguments:)' instead. >>> >>> Jordan >>&g

Re: [swift-users] Passing variadic C args through?

:)' instead. > > Jordan > > >> On Nov 14, 2017, at 17:19, Rick Mann via swift-users <swift-users@swift.org> >> wrote: >> >> I've had a long-working `debugLog()` method that looks like this: >> >> ``` >> func >> debugLog(_ inMsg: T, fi

[swift-users] Passing variadic C args through?

I've had a long-working `debugLog()` method that looks like this: ``` func debugLog(_ inMsg: T, file inFile : String = #file, line inLine : Int = #line) { let file = (inFile as NSString).lastPathComponent let s = "\(file):\(inLine)\(inMsg)" print(s) } ``` I wanted to

Re: [swift-users] Modulo operation in Swift?

Why is % not available for floating point numbers? > On Nov 9, 2017, at 04:51 , Martin R via swift-users > wrote: > > There was a discussion in swift-evolution, starting at > > > https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20160516/018521.html > >

Re: [swift-users] .apinotesc file placement?

bust and complete module map or apinotes file. I'd love to be able to include both of those *outside* of the framework, so that I don't have to modify their provided items in any way. But for now, I can drop both files into the Framework they provide. Thanks! > > Jordan > > >

[swift-users] .apinotesc file placement?

I'm using a third-party C library shoehorned into a Framework. It does not have proper ENUM macros nor an apinotes file. I'd like to add one. I'm using Xcode 9. • Can I put the .apinotesc file in the Framework somewhere? • Can I make Xcode automatically compile it? Thanks. -- Rick Mann

Re: [swift-users] Re-initializing lazy vars

by adding a consistent syntax for other >> behaviors. I think. I wish I could remember who'd brought up the idea... >> they'd probably know straight away if that's what happened. >> >> - Dave Sweeris >> >>> On Oct 19, 2017, at 5:40 PM, Rick Mann via swift-users

[swift-users] Re-initializing lazy vars

Googling for the answer, it seemed some versions of Swift supported setting a lazy var property to nil, such that the next time it's accessed, the initializer would be run again. But I just tried this in a playground in Swift 4 and it doesn't work. It sure seems to me like it should work.

Re: [swift-users] Swift-C array interop with Swift 4/Xcode 9

that. > On Sep 20, 2017, at 17:03 , Rick Mann via swift-users <swift-users@swift.org> > wrote: > > I've got Swift code wrapping a C API. One of the C structs the API uses looks > like this: > > typedef struct { >size_t size; >float transformation[16]; >float

[swift-users] Swift-C array interop with Swift 4/Xcode 9

I've got Swift code wrapping a C API. One of the C structs the API uses looks like this: typedef struct { size_t size; float transformation[16]; float projection[16]; uint32_t width; uint32_t height; } image_info_t; In Swift, the two array members are 16-tuples of floats.

Re: [swift-users] Swift 4 "Cannot use mutating member on immutable value: 'self' is immutable"

from O(n^2) to O(n^3), which is quite a change. > > On 16 Sep 2017, at 01:44, Rick Mann via swift-users <swift-users@swift.org> > wrote: > >> Is the compiler looking at the name "pop" and adding additional constraints >> (and then spewing a bogus error mess

Re: [swift-users] Swift 4 "Cannot use mutating member on immutable value: 'self' is immutable"

In my case, it's my own implementation of popFirst(), so I'm not sure why it's complaining at all. Who cares if it's slow? The declaration is identical to popLast(), with the exception that I'm defining mine in an extension that's not Generic (I don't know if you can do it any other way). But

Re: [swift-users] Swift 4 "Cannot use mutating member on immutable value: 'self' is immutable"

>>> it or post it here. >>> >>> Zhao Xin >>> >>> On Thu, Sep 14, 2017 at 9:36 AM, Roderick Mann <rm...@latencyzero.com> >>> wrote: >>> Yeah, that's not it. I made the change you suggested, I get the same error. >>> >

Re: [swift-users] dynamic requires @objc in Framework, but not in monolithic project

>> >> >> >>> On Sep 13, 2017, at 17:06 , Hooman Mehr <hoo...@mac.com> wrote: >>> >>> When you create a new project in Xcode 9, the defaults for compiler >>> settings are different. The errors you see are the result of running in &

[swift-users] dynamic requires @objc in Framework, but not in monolithic project

I have an iOS app in which I'm factoring out code into a Framework. In Xcode 9 GM (Swift 4), the code builds fine when it's a monolithic app, but some of the files I've pulled into the framework are no longer compiling. One of the errors is: Model.swift:471:14: 'dynamic' var 'dateCreated' must

[swift-users] API notes and modulemap in Frameworks?

I'm not sure if this is a Swift question, or an Xcode question. When building a Swift-based Framework for distribution to third parties, where do the apinotes and modulemap files go? Thanks. -- Rick Mann rm...@latencyzero.com ___ swift-users

[swift-users] Extracting arbitrary types (e.g. UInt16) out of Data

I continue to struggle with the "proper" and most efficient way to do things with Data. In this case, I have a set of bytes received over a serial port in a Data. The last two bytes are a (big- or little-endian) UInt16 CRC. However, there maybe an odd or even number of bytes in the Data before

Re: [swift-users] Help! Slicing an array is very expensive

> On May 10, 2017, at 11:52 , Joe Groff <jgr...@apple.com> wrote: > > >> On May 8, 2017, at 4:47 PM, Rick Mann via swift-users >> <swift-users@swift.org> wrote: >> >> I have this C library that interacts with some hardware over the network >>

Re: [swift-users] Making Error sub-enums Equatable

> On May 10, 2017, at 01:23 , Brent Royal-Gordon <br...@architechies.com> wrote: > >> On May 8, 2017, at 2:01 AM, Rick Mann via swift-users >> <swift-users@swift.org> wrote: >> >> Seriously, I've been googling this for a half-hour, and I can't fi

[swift-users] Help! Slicing an array is very expensive

I have this C library that interacts with some hardware over the network that produces a ton of data. It tells me up front the maximum size the data might be so I can allocate a buffer for it, then does a bunch of network requests downloading that data into the buffer, then tells me when it's

[swift-users] Making Error sub-enums Equatable

Seriously, I've been googling this for a half-hour, and I can't find an answer (everything that comes up is for ErrorType, absolutely nothing for Error). I have an enum: enum MyErrors : Error { case one(String) case two case three(String) } let a: MyErrors = .one("foo") let b =

Re: [swift-users] Annotating C APIs without changing the original header files

I'm trying to use apinotes for this third-party C library (call it "Lib.dylib"). It has an enum lgs_error_t: typedef enum { lgs_error_none = 0, lgs_error_invalid_handle = -1, lgs_error_null = -2, lgs_error_invalid_parameter = -3, lgs_error_invalid_operation = -4,

Re: [swift-users] Slicing a [UInt8] into a Data without copying?

gt; let slice = bytes[0..<4] > slice.withUnsafeBytes { buffer in > let d = Data(bytesNoCopy: UnsafeMutableRawPointer(mutating: > buffer.baseAddress!), count: buffer.count, deallocator: .none) > // whatever you do, dont let d escape > } > > > >> On May 4, 2017, at 16:31,

[swift-users] Slicing a [UInt8] into a Data without copying?

Is it possible to make a (immutable) Data() object from a slice of a [UInt8] and avoid copying the data? -- Rick Mann rm...@latencyzero.com ___ swift-users mailing list swift-users@swift.org https://lists.swift.org/mailman/listinfo/swift-users

Re: [swift-users] Any way to declare a method that suppresses the string interpolation warning?

t; >>> On Apr 22, 2017, at 12:23 , Saagar Jha <saa...@saagarjha.com> wrote: >>> >>> >>> Saagar Jha >>> >>>> On Apr 21, 2017, at 04:35, Rick Mann via swift-users >>>> <swift-users@swift.org> wrote: >>>> &

Re: [swift-users] Why does withUnsafePointer(to:) require a var argument?

Yeah, okay. So: how do I do this in a way that is safe? -- Rick Mann rm...@latencyzero.com > On Apr 27, 2017, at 23:00, Rien wrote: > > To address your question: > > https://developer.apple.com/reference/foundation/data/1779823-withunsafemutablebytes > > "Warning >

Re: [swift-users] Why does withUnsafePointer(to:) require a var argument?

> On Apr 27, 2017, at 18:56 , Hooman Mehr wrote: > > You should be able to type your `dataBuffer ` as [Int8] (Byte array). Then > you won’t need `withUnsafeMutableBytes`. You can simply call it like this: > > self.request = c_library_call(, dataBuffer) // Call as if it is a C

Re: [swift-users] Why does withUnsafePointer(to:) require a var argument?

C > array > > It works because of C interoperability compiler magic. > > As long as the instance holding `dataBuffer` is not deallocated and you have > not resized the array, the pointer should remain valid. > >> On Apr 27, 2017, at 4:38 PM, Rick Mann via swift-users &

Re: [swift-users] Why does withUnsafePointer(to:) require a var argument?

> On Apr 27, 2017, at 01:48 , Alex Blewitt wrote: > ... > The let constant may not even be stored in a single place; if it's known to > be constant it can be in-lined at the point of use and potentially unpacked > and dead code elimination throw away the unused members, for

Re: [swift-users] Why does withUnsafePointer(to:) require a var argument?

be >> able to derive its pointer. The languages requires inout arguments to be >> vars, leading to withUnsafePointer() requiring the passed object to be a var. >> >> There may be other subtleties I'm not aware of, though. >> >>> Le 27 avr. 2017 à 02:42, Rick Man

[swift-users] Why does withUnsafePointer(to:) require a var argument?

We have withUnsafePointer(to:) and withUnsafeMutablePointer(to:). Why does the first take an inout parameter? The function names imply that the first will not modify the pointer (which I take to mean its contents), and it makes it quite clunky to pass in constant things. -- Rick Mann

[swift-users] Any way to enhance C interop "out-of-band?"

I'm using a third-party C library whose header doesn't properly tag things like enums, and so they show up in Swift without their cases. Is there any way to write an auxiliary file to help the compiler do the conversion (e.g. something in the modulemap file), so that I don't have to modify the

[swift-users] Still having trouble with C interop (passing buffers)

I'm trying to pass a Data of allocated size to a C function for it to fill in: lib_example_call(_ params: UnsafePointer!, _ data: UnsafeMutableRawPointer!) ... { self.dataBuffer = Data(capacity: BufferSizeConstant) var params = lib_call_params_t(); params.data_capacity =

Re: [swift-users] withUnsafeMutableBytes is killing me

ointer > ) -> Void in > // ... > } > > > On 25.04.2017 10:45, Rick Mann via swift-users wrote: >> The following playground reproduces an issue I'm having, in that the code >> won't compile depending on the content of the closure. In fact, an empty >>

[swift-users] withUnsafeMutableBytes is killing me

The following playground reproduces an issue I'm having, in that the code won't compile depending on the content of the closure. In fact, an empty closure is fine, but when I try to call certain things, it's not. I figure it has something to do with the type inference for inPointer, but I

Re: [swift-users] 'inout Data' is not convertible to 'Data'

Oh wow, it's the debugLog() call! If that's inside the block, it fails to compile. > On Apr 24, 2017, at 14:18 , Rick Mann via swift-users <swift-users@swift.org> > wrote: > > I could swear this was compiling a couple days ago, as I was making the call > inside

[swift-users] 'inout Data' is not convertible to 'Data'

I could swear this was compiling a couple days ago, as I was making the call inside the block and dealing with issues around that. Can anyone explain what's going on here? class MyClass { func execute() { self.dataBuffer = Data(capacity: lgsImageDataSize)

Re: [swift-users] Any way to declare a method that suppresses the string interpolation warning?

> On Apr 22, 2017, at 12:23 , Saagar Jha <saa...@saagarjha.com> wrote: > > > Saagar Jha > >> On Apr 21, 2017, at 04:35, Rick Mann via swift-users <swift-users@swift.org> >> wrote: >> >> I have a debugLog() method that looks like this: &g

Re: [swift-users] Importing empty C structs

> On Apr 18, 2017, at 09:11 , Joe Groff <jgr...@apple.com> wrote: > > >> On Apr 17, 2017, at 6:19 PM, Rick Mann via swift-users >> <swift-users@swift.org> wrote: >> >> I'm trying to make a module out of a C library and header file. It has

Re: [swift-users] Can't access Swift class from Objective-C

mentation reason for this; > it's not just the compiler being capricious.) > - In frameworks, only public and open classes are included in the generated > header, since it's part of your framework's public interface. > > Are you in any of these situations? > > Jordan > >

Re: [swift-users] Cannot subclass a class with objc_subclassing_restricted attribute

> On Apr 17, 2017, at 08:54 , Joe Groff <jgr...@apple.com> wrote: > > >> On Apr 14, 2017, at 7:41 PM, Rick Mann via swift-users >> <swift-users@swift.org> wrote: >> >> I'm refactoring some Objective-C code to inherit from a new Swift super >

[swift-users] Can't access Swift class from Objective-C

My Objective-C file is importing "Module-Swift.h", and that file has some of my other Swift classes, but not the one I just wrote. I've tried making the class public, but I didn't need to do that on any of the others. I've tried cleaning the build folder of my Xcode project, but I get the same

[swift-users] Importing empty C structs

I'm trying to make a module out of a C library and header file. It has at least one empty struct: struct lgs_context_t {}; and a function: LGS_EXPORT struct lgs_context_t* lgs_init(const lgs_context_params_t* params); Swift sees the function, I can call it and assign the result to a variable,

Re: [swift-users] Cannot subclass a class with objc_subclassing_restricted attribute

> On Apr 14, 2017, at 22:33 , Guillaume Lessard <gless...@tffenterprises.com> > wrote: > > Your class probably needs to be declared as open. > > @objc open class Camera : NSObject {} Thanks. Sadly, that does not fix it. > Guillaume Lessard > >> On A

[swift-users] Cannot subclass a class with objc_subclassing_restricted attribute

I'm refactoring some Objective-C code to inherit from a new Swift super class. This has been going okay, and I've been cleaning up build errors as I spot them (some auxiliary enums caused enum name changes, etc.). But my last error seems to be that I can't subclass the Swift class: "Cannot

[swift-users] Linux equivalent of macOS/iOS run loop, aka libdispatch/Dispatch on Linux

I've got Swift and libdispatch installed and linking under Ubuntu 16.04, but I'm not sure how to set up the Linux equivalent of the macOS run loop in order to service all the dispatch queues. I'm having a hard time finding an example of how to do this. Some GCD C code calls dispatch_main()

Re: [swift-users] for with optional collection?

y? { }" — to parallel "for > case let x? in array { }" > > >> On Fri, Feb 10, 2017 at 1:03 PM, Rick Mann via swift-users >> <swift-users@swift.org> wrote: >> I love the idea of for in? (Or even for? In). You should pitch that to >> evolution

Re: [swift-users] for with optional collection?

I love the idea of for in? (Or even for? In). You should pitch that to evolution. Sent from my iPhone > On Feb 10, 2017, at 07:04, Tino Heth <2...@gmx.de> wrote: > > >> Is there any concise way to write the following? >> >> if let collection = someOptionalCollection >> { >>for item in

Re: [swift-users] for with optional collection?

> On Feb 9, 2017, at 13:31 , Saagar Jha wrote: > > for item in someOptionalCollection ?? [] { > item.doSomething() > } > Thanks, this is probably the closest. Sadly I can't seem to test downcasting because Playgrounds just stop working, with no feedback, for this

[swift-users] for with optional collection?

Is there any concise way to write the following? if let collection = someOptionalCollection { for item in collection { } } I can imagine more complicated things, too: if let collection = someOptionalCollection as? [SomeType] { for item in collection { } } It would be

Re: [swift-users] ANTLR 4.6 now generates parsers in Swift

Awesome! > On Dec 15, 2016, at 22:11 , Terence Parr via swift-users > wrote: > > Dear Swift-users! Just a quick note that I finally got the Swift code > generation target for the ANTLR 4 parser generator integrated and released! > You can see the release notes here: >

Re: [swift-users] Changing precedence of / operator for my protocol?

gt; > -- Howard. > > On 30 November 2016 at 09:28, Greg Parker via swift-users > <swift-users@swift.org> wrote: > > > On Nov 29, 2016, at 2:55 AM, Rick Mann via swift-users > > <swift-users@swift.org> wrote: > > > > Working on dimensional anal

[swift-users] Changing precedence of / operator for my protocol?

Working on dimensional analysis, I have some proof-of-concept code that seems to be working: let n1 = kilogram * meter / second * second ([(kg⋅m) / s]⋅s) let n2 = kilogram * meter / (second * second) [(kg⋅m) / (s⋅s)] Note: () around unit products, [] around unit quotients.

[swift-users] Dimensional analysis

My earlier post about converting Decimal to Double was part of a larger effort by me to write a calculator app that supports dimensional analysis/unit conversions. I've explored some existing libraries on the topic, ranging from this one in Common Lisp

Re: [swift-users] Extending Arrays of specific type, and specialization

>>>>>> >>>>>>> Instead, a family of overloaded global functions gives you the most >>>>>>> coverage and best performance, at the expense of repetition and >>>>>>> boilerplate code: >>>>>>> >&

Re: [swift-users] Extending Arrays of specific type, and specialization

; var result: S.Iterator.Element = 0 >>>>> for element in sequence { result += element } >>>>> return result >>>>> } >>>>> >>>>> func sum(_ array: Array) -> Double { >>>>> var result = Double() >>>

Re: [swift-users] Any equivalent to Java's AtomicInteger?

nsive. Perhaps the compiler magically optimizes this down to an atomic instruction, but I doubt it. BTW, is there any easy way to see the generated assembly? Seems to be a missing feature in Xcode. > >> On Nov 21, 2016, at 7:55 PM, Rick Mann via swift-users >> <swift-users@sw

Re: [swift-users] Extending Arrays of specific type, and specialization

as already discussed and dismissed. > > > > > -- > Adrian Zubarev > Sent with Airmail > > Am 22. November 2016 um 01:32:42, Rick Mann via swift-users > (swift-users@swift.org) schrieb: > >> My googling is not turning up an answer that works in Xcode 8.

Re: [swift-users] Extending Arrays of specific type, and specialization

> On Nov 22, 2016, at 03:04 , Tino Heth <2...@gmx.de> wrote: > > Hi Rick, > > as evolution is somewhat paused, swift-users seems to gain more traction ;-) > > Imho the most natural would be > extension Array { > … > } > > I hope to see this addition included when the topic is discussed again.

[swift-users] Any equivalent to Java's AtomicInteger?

A lot of architectures provide CPU support for atomic increment and the like. does, too, but most of it is unavailable in Xcode 8.1. Is there a Swift AtomicInteger? Is that worth adding to the language? -- Rick Mann rm...@latencyzero.com ___

Re: [swift-users] Bool to Int

> On Nov 21, 2016, at 15:09 , Marco S Hyman wrote: > >> Except it does, because if I write >> >> let a = 2 > >> a is of type Int (at least, according to Xcode's code completion). > > and if you write > > let b = 2 + 0.5 > > 2 is treated as a double. The type of

Re: [swift-users] Bool to Int

> On Nov 21, 2016, at 09:46 , Kenny Leung via swift-users > wrote: > > This is so confusing. "Literals are untyped", but there’s a “BooleanLiteral”, > which is obviously of type Boolean. Agreed. -- Rick Mann rm...@latencyzero.com

Re: [swift-users] Bool to Int

r now I'm doing what I need with branching, but it would be nice to find a more efficient way. > > > Jon > >> On Nov 20, 2016, at 10:48 PM, Rick Mann via swift-users >> <swift-users@swift.org> wrote: >> >> It seems I can't do this: >&

[swift-users] Bool to Int

It seems I can't do this: let r = Int(a > b) but I can do it with a literal: let r = Int(true) I'd like to do this to implement signum without branching, but perhaps that's not possible. -- Rick Mann rm...@latencyzero.com ___ swift-users mailing

Re: [swift-users] Implementing signum

it is better to extend the existing `SignedNumber` > protocol instead of introducing your own `Signumable`, unless if you need to > write other generic algorithms that need your protocol as their constraints. > >> On Nov 19, 2016, at 6:44 PM, Rick Mann via swift-users >> <swift-

[swift-users] Implementing signum

I'm trying to do this: protocol Signumable { func sgn() -> Self } extension Signumable { func sgn() -> Self { let pos = 0 < self // Error let neg = self < 0 // Error let p

Re: [swift-users] Attempting to call default protocol implementation crashes Playground

hould not consider it like something super class does. If you want it that > way, use class inheritance instead. > > Zhaoxin > > Get Outlook for iOS > > _____________ > From: Rick Mann via swift-users <swift-users@swift.org> > Sent: 星期三, 十一月 16, 2016 07

Re: [swift-users] Attempting to call default protocol implementation crashes Playground

rint("fooFunc FooClass") > } > } > > let fc = FooClass() > fc.fooFunc() > > Dan > > On Tue, Nov 15, 2016 at 4:28 PM, Rick Mann via swift-users > <swift-users@swift.org> wrote: > The following gives Xcode 8.1 a very hard time. Eventually I get a B

Re: [swift-users] Reflection in Swift 3?

ective-C anyway, >>> because, if you don’t know what’s in the string, you need to validate it >>> (imagine if the user of your app finds out that they can cause you to >>> instantiate any arbitrary class) and if you do know what’s in the string, >>> why are

Re: [swift-users] Reflection in Swift 3?

2016, at 22:47 , David Sweeris <daveswee...@mac.com> wrote: >>> >>> >>>> On Nov 13, 2016, at 00:38, Rick Mann via swift-users >>>> <swift-users@swift.org> wrote: >>>> >>>> So, it seems there's still no way to do something

Re: [swift-users] Reflection in Swift 3?

> On Nov 12, 2016, at 22:47 , David Sweeris <daveswee...@mac.com> wrote: > > >> On Nov 13, 2016, at 00:38, Rick Mann via swift-users <swift-users@swift.org> >> wrote: >> >> So, it seems there's still no way to do something like instantiate

Re: [swift-users] Misleading? cannot subscript a value of type 'inout [PathPoint]' with optional field

ment type 'inout CGPoint' > points[0].anchorPt += dv > ~~^~~~ > > but that's still not great. So, yes, please do file a bug at bugs.swift.org. > > Thank you! > Jordan > >> On Nov 11, 2016, at 13:29, Rick Mann via swift-users <swift-users@swift.

[swift-users] Misleading? cannot subscript a value of type 'inout [PathPoint]' with optional field

I think the error I'm getting here is misleading. Should I file a bug? import CoreGraphics func +=(inLHS : inout CGPoint, inRHS : CGPoint) { inLHS.x += inRHS.x inLHS.y += inRHS.y } struct PathPoint { varanchorPt:CGPoint? } var points = [PathPoint()] let dv = CGPoint(x: 0,

Re: [swift-users] Why can I not filter or map a dictionary to another dictionary?

> On Oct 27, 2016, at 10:29 , Dave Abrahams wrote: > > > on Thu Oct 27 2016, Rick Mann wrote: > >>> On Oct 26, 2016, at 22:23 , Dave Abrahams via swift-users >>> wrote: >>> >>> >>> on Wed Oct 26 2016, Rick Mann wrote: >>> >> It seems

Re: [swift-users] Why can I not filter or map a dictionary to another dictionary?

C"] >let sd = bd.filter{(k, v) in >k > 1} >dump(sd) In this example, sd is an array of tuples of (key, value), not a dictionary. > >On 27/10/2016, 01:12, "Rick Mann via swift-users" > <swift-users-boun...@swift.org on behalf of swift-

Re: [swift-users] Why can I not filter or map a dictionary to another dictionary?

> On Oct 26, 2016, at 22:23 , Dave Abrahams via swift-users > wrote: > > > on Wed Oct 26 2016, Rick Mann wrote: > >> It seems fairly natural to want to do this: >> >> let bigDictionary = ... >> let smallerDictionary = bigDictionary.filter { key, value in > returning

[swift-users] Why can I not filter or map a dictionary to another dictionary?

It seems fairly natural to want to do this: let bigDictionary = ... let smallerDictionary = bigDictionary.filter { key, value in } Similarly, it seems natural to want to map this way. Am I overlooking something? -- Rick Mann rm...@latencyzero.com

[swift-users] Implementing += for optional arrays

When working with URLComponents query items, it would be nice to write code like this: var oqi: [URLQueryItem]? = [..., ..., ...] var comps = URLComponents(…) comps.queryItems += oqi The problem is that queryItems is [URLQueryItem]?, and so I can't just append. I'd like to write a version of

Re: [swift-users] Overload by return type optionality?

> On Oct 13, 2016, at 14:51 , Greg Parker <gpar...@apple.com> wrote: > >> >> On Oct 13, 2016, at 2:36 PM, Rick Mann via swift-users >> <swift-users@swift.org> wrote: >> >> It seems I can write this: >> >> extension String >

[swift-users] Overload by return type optionality?

It seems I can write this: extension String { public func deleting(prefix inPrefix: String) -> String public func deleting(prefix inPrefix: String) -> String? } But I was hoping it would do the right thing: let a = s.deleting(prefix: "foo") if let b = s.deleting(prefix: "foo") { } But it

Re: [swift-users] @escaping may only be applied to parameters of function type

s list regarding do >> this topic, not in a situation to search for it. It is a short coming in how >> escaping can be applied to things like optional closures. >> >> I was in the process of authoring an email for swift evolution about it and >> haven't yet gotten a

[swift-users] @escaping may only be applied to parameters of function type

I'm trying to write this function. The errorHandler: parameter is modeled after the NSFileManager enumerate() function. If I include the @escaping you see there, I get the error "@escaping may only be applied to parameters of function type". The second parameter, iterator:, seems to have no

Re: [swift-users] Lazy expression is ambiguous?

> On Sep 12, 2016, at 00:53 , Quinn The Eskimo! via swift-users > wrote: > > > On 12 Sep 2016, at 08:46, Rick Mann wrote: > >> I had assumed lazy worked like static, which I understand uses dispatch_once >> under the hood. > > Correct. > >

Re: [swift-users] Lazy expression is ambiguous?

> On Sep 12, 2016, at 00:02 , Quinn The Eskimo! via swift-users > wrote: > > > On 12 Sep 2016, at 06:40, Jacob Bandes-Storch via swift-users > wrote: > >> I'd recommend filing a bug at bugs.swift.org. > > Agreed. Done.

Re: [swift-users] Lazy expression is ambiguous?

ct Bar { > init(x: Int, y: Int? = 42) { } > } > > class Foo { > lazy var myQ = Bar(x: 3) > } > > > I'd recommend filing a bug at bugs.swift.org. > > On Sun, Sep 11, 2016 at 10:19 PM, Rick Mann via swift-users > <swift-users@swift.org> wrote: > I g

[swift-users] Lazy expression is ambiguous?

I get this error in the following code: "Type of expression is ambiguous without more context", on the DispatchQueue. But only if I mark it as "lazy", and not if I don't. I'm not sure why. class myClass { lazy var myQ = DispatchQueue(label: "Op", attributes: .concurrent)// <-- ERROR

Re: [swift-users] Closure typing changed in Swift 3

Sep 9, 2016, at 14:34 , Rick Mann via swift-users <swift-users@swift.org> > wrote: > > I have some code that implements an HTTP server. You use it like this: > > server["/some/path"] = > { inReq in > return .ok(.json(["key" : "valu

[swift-users] Closure typing changed in Swift 3

I have some code that implements an HTTP server. You use it like this: server["/some/path"] = { inReq in return .ok(.json(["key" : "value"])) } ".ok" is a case in the HttpResponse enum. The subscript on "server" above looks like this: class HttpServer { typealias Handler =

[swift-users] Argument type 'Int' does not conform to expected type 'AnyObject'

I've seen old (pre-Swift 3) posts online (e.g. http://stackoverflow.com/questions/28920232/why-do-integers-not-conform-to-the-anyobject-protocol) that address this, but my code worked yesterday before I used Xcode 8 GM to migrate it to Swift 3, and now it doesn't, so I'm trying to understand

[swift-users] protocols, optional, and public

I'm wrapping CLLocationManager (and its delegate), and I'm trying to create a protocol like this. This is directly cribbed from CLLocationManagerDelegate. --- public protocol LZLocationManagerDelegate : NSObjectProtocol { optional public func locationManager(manager:

Re: [swift-users] Swift in bare-metal embedded programming/Swift runtime

piler to yell at >> you for doing overhead-inducing stuff in a loop, for example. >> >> Anyway, best of luck :-) >> >> - Dave Sweeris >> >>> On Aug 9, 2016, at 15:10, Rick Mann via swift-users <swift-users@swift.org> >>> wrote: >

Re: [swift-users] Swift in bare-metal embedded programming/Swift runtime

> On Aug 10, 2016, at 09:31 , Jens Alfke wrote: > > If you’re going for something bigger than that, why not just use a Raspberry > Pi or C.H.I.P. or one of the other tiny ARM PC boards? They all run Linux, > and I believe people are already working on porting Swift to run

Re: [swift-users] Protocol with instance var that's set on construction, otherwise read-only

> On Aug 9, 2016, at 08:24 , Karl <razie...@gmail.com> wrote: > > >> On 3 Aug 2016, at 02:01, Rick Mann via swift-users <swift-users@swift.org> >> wrote: >> >> It complains if I make it a let because computed properties must be var. >> Becau

[swift-users] Swift in bare-metal embedded programming/Swift runtime

Is it possible to use Swift for bare-metal programming on embedded devices? These devices usually have memory-mapped registers that are read and written to affect the operation of the device. Some can be quite small (e.g. 8-bit registers, simple single physical memory address space), and others

Re: [swift-users] Protocol with instance var that's set on construction, otherwise read-only

> On Aug 3, 2016, at 03:23 , Dan Loewenherz <d...@lionheartsw.com> wrote: > > On Wed, Aug 3, 2016 at 3:51 AM, Rick Mann via swift-users > <swift-users@swift.org> wrote: > > > On Aug 2, 2016, at 19:06 , Jordan Rose <jordan_r...@apple.com> wrote: >

Re: [swift-users] Protocol with instance var that's set on construction, otherwise read-only

be too easy to break, and could be disallowed, requiring conforming types to create storage for the property and set it in init()). > > Jordan > > >> On Aug 2, 2016, at 17:01, Rick Mann via swift-users <swift-users@swift.org> >> wrote: >> >> It complain

  1   2   >