shiz(しず)@翻訳本執筆 (@stzn3) 's Twitter Profile
shiz(しず)@翻訳本執筆

@stzn3

福岡在住のiOSエンジニア。新刊『ストリートコーダー』発売中 (正誤表は公式ページ参照)。 『Good Code, Bad Code』『クリエイティブプログラマー』などを共同執筆(翻訳)。カンファレンスの運営、登壇やSwift言語ガイド日本語版の作成なども行なっている。

ID: 937075654129942528

linkhttps://github.com/stzn calendar_today02-12-2017 21:47:00

7,7K Tweet

2,2K Followers

348 Following

iOSDC Japan (@iosdcjp) 's Twitter Profile Photo

たくさんのプロポーザル、ありがとうございました! プロポーザル募集は恒例のアディショナルタイムに突入しました。明日2日午後まで開けておきますので滑り込みご応募、お待ちしています! #iosdc

shiz(しず)@翻訳本執筆 (@stzn3) 's Twitter Profile Photo

make the user ID part of the key, and also store the timestamp in the cached value; writing a value into the cache would now become an atomic operation that drops the w forums.swift.org/t/passing-larg…

shiz(しず)@翻訳本執筆 (@stzn3) 's Twitter Profile Photo

Error -60008 is errAuthorizationInternal, which does indeed suggest that this is problem with the way that your executable is built. forums.swift.org/t/swift-build-…

shiz(しず)@翻訳本執筆 (@stzn3) 's Twitter Profile Photo

👀 pretty skeptical of using detached just to disable inheritance; I would generally prefer moving the code to an @ concurrent async function and calling that from the Task (or eliminating the Task entirely if the caller is also async). forums.swift.org/t/task-and-tas…

shiz(しず)@翻訳本執筆 (@stzn3) 's Twitter Profile Photo

When importing methods from Objective-C, the compiler understands something about how they're conventionally used, including that completion handlers are generally called from different concurrent contexts and therefore need to be @Sendable (and Joe Vance) forums.swift.org/t/passing-non-…

shiz(しず)@翻訳本執筆 (@stzn3) 's Twitter Profile Photo

usually work around this sort of issue by adding -Xfrontend -alias-module-names-in-module-interface to the OTHER_SWIFT_FLAGS build setting for the module in question. forums.swift.org/t/frameworknam…

shiz(しず)@翻訳本執筆 (@stzn3) 's Twitter Profile Photo

👀 a closure literal passed to initialize a Task that is instantiated within a function with an isolated parameter will currently only inherit the isolation of the enclosing function if the function's isolated parameter itself is strongly captured by the closure.

👀
a closure literal passed to initialize a Task that is instantiated within a function with an isolated parameter will currently only inherit the isolation of the enclosing function if the function's isolated parameter itself is strongly captured by the closure.
shiz(しず)@翻訳本執筆 (@stzn3) 's Twitter Profile Photo

👀 stdlib exercises almost every part of the frontend, and the compiler and stdlib often move in lockstep...also some brittleness in associated type inference so for example changing the order of declarations or source files can break the stdlib build. forums.swift.org/t/type-checker…