savchenkovaleriy / emacs-swift-module Goto Github PK

Environment lifetimes can be tricky and we should add defensive checks for using it past it lifetime or outside of its thread.

Right now, we need Swift 5.6 only for DoCC and we can request it only when building the docs.

Thanks for the great package. I have used it developing multiple dynamic modules. However, when I loading the modules constructed with emacs-swift-module, it throws warning as the following:

objc[49686]: Class _TtC16EmacsSwiftModule9LazyHook0 is implemented in both libEMT.dylib (0x12a405080) and libmacime.dylib (0x129ba6f78).

One of the two will be used. Which one is undefined.

I guess it is because the symbol name within two modules are duplicated. And I want to know how to solve the warning.

The package is great, and I'm writing a swift module with it.

However, I found that the commit c776706 fixes a bug (which I encountered in version 1.3.2) related to string conversion. But no new releases are published.

Can we publish a new release 1.3.3 based on commit c776706?

Thanks for this great package. I am already using it for a few functions ported from python + objc.

I had this bug where the output (a string) is different on Emacs than on Swift. The emacs one looks truncated.

try env.defun("get-definition") {
    (phrase: String) -> String? in
    let ns = phrase as NSString
    let range = CFRange(location: 0, length: ns.length)
    guard let definition = DCSCopyTextDefinition(nil, ns, range) else {
        return nil
    }
    let s = String(definition.takeUnretainedValue())
    print(s)
    return s
}

Use get-definition on the word "select" and observe the difference between the return value and what is printed on the console. I could produce this on macOS 13.4 and Swift 5.8.