[swift-users] Cancelling an SPM build cleanly

2017-11-07 Thread Geordie J via swift-users
I was just reminded of this issue by another thread (thanks Daniel Dunbar for https://github.com/apple/swift-llbuild/pull/196 !) Is it possible to cancel an SPM build cleanly? If I run swift build and then press Ctrl-C halfway through I end up

Re: [swift-users] SwiftProtobuf unable to link on Ubuntu

2017-10-14 Thread Geordie J via swift-users
Hi Edward, > Am 14.10.2017 um 22:35 schrieb Edward Connell : > > Hi Geordie, > That is actually a capital "I" eye for import > This font make an eye and elle look the same. This is the build line I am > trying to use. My apologies. > > swift build -Xswiftc

Re: [swift-users] SwiftProtobuf unable to link on Ubuntu

2017-10-14 Thread Geordie J via swift-users
Hi > Am 14.10.2017 um 21:55 schrieb Edward Connell via swift-users > : > > Has anyone used the SwiftProtobuf module on Linux? > https://github.com/apple/swift-protobuf > > > I am able to successfully generate swift classes from

Re: [swift-users] [swift-build-dev] SwiftPM manual dependency management

2017-07-22 Thread Geordie J via swift-users
Thanks for the update on this one. Judging by the thread, it looks like it’ll need to be handled internally by Apple. Also, I have no idea how to reply to the existing post without breaking the internet so I’m going to just wait patiently instead.. > Am 23.07.2017 um 01:11 schrieb David

Re: [swift-users] [swift-build-dev] SwiftPM manual dependency management

2017-07-22 Thread Geordie J via swift-users
> Am 22.07.2017 um 19:46 schrieb David Sweeris : > > > > Sent from my iPhone > >> On Jul 22, 2017, at 05:16, Geordie Jay via swift-build-dev >> wrote: >> >> How can I get involved in the evolution of this? The evolutions are always >>

Re: [swift-users] SwiftPM manual dependency management

2017-07-21 Thread Geordie J via swift-users
it, thanks for your reply. >> >>> Am 21.07.2017 um 07:33 schrieb Ankit Aggarwal via swift-users >>> <swift-users@swift.org <mailto:swift-users@swift.org>>: >>> >>> >>> >>> On Thu, Jul 20, 2017 at 10:34 PM, Geordie J via sw

Re: [swift-users] SwiftPM manual dependency management

2017-07-21 Thread Geordie J via swift-users
Hi Ankit, thanks for your reply. > Am 21.07.2017 um 07:33 schrieb Ankit Aggarwal via swift-users > <swift-users@swift.org>: > > > > On Thu, Jul 20, 2017 at 10:34 PM, Geordie J via swift-users > <swift-users@swift.org <mailto:swift-users@swift.org>&

[swift-users] SwiftPM manual dependency management

2017-07-20 Thread Geordie J via swift-users
Hi all, My team and I are trying to use SwiftPM to develop a relatively complex app with multiple dependencies, all of which are being developed locally and in parallel. The reason for this is compatibility with an existing module/import structure used by our iOS app. Maybe I’m doing something

Re: [swift-users] How to write better Swift

2017-07-10 Thread Geordie J via swift-users
Would "didSet" on a normal variable work for you? var status: Int { didSet { doSomething() } } Geordie > Am 10.07.2017 um 17:34 schrieb Gerriet M. Denkmann via swift-users > : > > This works (Xcode Version 8.3.2 (8E2002)): > > class SomeClass > { > private var

Re: [swift-users] Compile time exceeded. Anything wrong?

2017-06-06 Thread Geordie J via swift-users
Interesting, I guess it’s anything with multiple possible function overloads then! It looks pretty trivial though to figure out the two components before trying to figure out which function, which should lead to the result in a reasonable time. There must be something else going on. Good work

Re: [swift-users] Calling default implementation of protocol methods as selectors

2017-06-04 Thread Geordie J via swift-users
In fact, this would be even better (avoids unnecessary implicitly unwrapped optionals): class ClosureGestureRecognizer { fileprivate var recognizer: GestureRecognizer private var onAction: ((GestureRecognizer) -> Void) init(onAction: @escaping ((GestureRecognizer) -> Void)) {

Re: [swift-users] Calling default implementation of protocol methods as selectors

2017-06-04 Thread Geordie J via swift-users
To get around the issue of using self on init, but also that of multiple recogniser types, try this: class ClosureGestureRecognizer { // These are initially nil and set on init to their desired values. // This gets around the issue of using self in init. // `private` means they can't

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

2017-05-12 Thread Geordie J via swift-users
: lgs_error_queue_full > SwiftName: lgs_error_t.queueFull > > But this line of code fails: > > var err: lgs_error_t = .nullParameter > Type 'lgs_error_t' has no member 'nullParameter' > > Am I missing something else? > > > On May 4, 2017, at 16:55 , Douglas Grego

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

2017-05-04 Thread Geordie J via swift-users
Hi everyone, I’m about to start on another big project with Swift on Android and would like to annotate that JNI headers as much as possible before I do: specifically I’d like to make _Nonnull and CF_SWIFT_NAME annotations to the headers found in a user's jni.h. The question is: is it

[swift-users] Using .gyb outside of the stdlib

2017-05-04 Thread Geordie J via swift-users
Hi again, another question: Is it possible to use .gyb files to automatically generate repetitive code outside of the stdlib? Preferably in a SwiftPM package? Here’s an example of what I’ve been using it for: https://github.com/SwiftAndroid/swift-jni/blob/master/JNIFields.swift.gyb