Milen Dzhumerov

Mixing Swift + Obj-C is supported but there are multiple caveats: - It's only officially supported for `apple_library` and `apple_test`.`apple_binary` is not supported at present. - In order to enable...

> This looks like pretty severe to me. Are there any workaround for this? There are no workarounds. Breakpoints still work, though, you just lose the ability to inspect variables...

> Is that because Swift librairies are compiled as static libs? Yes and no. The usage of static libs exposes an underlying bug. The details are documented in [SR-2660](https://bugs.swift.org/browse/SR-2660). >...

One aspect I forgot to mention is that you can still debug a single Swift module at a time (not ideal but at least it's something). This can be done...

@KieranLafferty I encountered the same issue when the `apple_binary` did not actually have any source files (all the code was in a mixed `apple_library` with an `@NSApplicationMain`). The solution is...

@KieranLafferty The names of Obj-C classes defined in Swift are mangled. You will usually something like: SWIFT_CLASS("_TtC9ComponentLibrary21AppDelegate") @interface AppDelegate: NSObject ... @end Instead, you should do the following: - In...

@KieranLafferty: > it can’t compile the Lib-swift.h (see my previous comment above) because the header tried to import another swift library of mine using @import which isn’t supported yet by...

On a related note, it would be good to expose and extract all the parsing code (namely -shapesFromNumbersInStrictASCIIRepresentation:) so that other apps can consume ASCIImage strings. Ideally, I'd want to...

I'm waiting to see how things pan out with ASCIImage Super Studio, as I don't want to end up duplicating work if possible. Is there any roadmap for the studio...

> ... generate ASCIImage-friendly strings ... Do we mean something like: ``` NSString* asciiImage = @"....."; ``` If so, that'd be quite easy to do and could be another option...