0xK4M1L 0xB0RZYM (@kam800) header
0xK4M1L 0xB0RZYM (@kam800) profile picture

pretending to be a software engineer

Warsaw
Joined December 2010
Photo by 0xK4M1L 0xB0RZYM (@kam800)Photo by 0xK4M1L 0xB0RZYM (@kam800)Photo by 0xK4M1L 0xB0RZYM (@kam800)Photo by 0xK4M1L 0xB0RZYM (@kam800)Photo by 0xK4M1L 0xB0RZYM (@kam800)Photo by 0xK4M1L 0xB0RZYM (@kam800)Photo by 0xK4M1L 0xB0RZYM (@kam800)Photo by 0xK4M1L 0xB0RZYM (@kam800)Photo by 0xK4M1L 0xB0RZYM (@kam800)Photo by 0xK4M1L 0xB0RZYM (@kam800)
@dgregor79 I have an unexpected pointer in the middle of a swift enum type metadata. A value witness table pointer comes first, then the unexpected pointer, then a kind, finally a nominal type descriptor. Should this happen at all? As far as I know kind should be right after VWT.
I will bury this iPod Touch 4 as a time capsule, so future generations could try to unlock it. (The message says “iPod is disabled, try again in 26 milion minutes”)
1
14
I gave a talk about Swift binary compatibility at Allegro Tech Live. It was entitled "Let’s decompile Swift ABI Stability". Why decompiling Swift while it's open sourced? Sometimes one assembly opcode is worth a thousand lines of code. 🤖 youtu.be/ubJurLCxAtw?t=218 #SwiftLang
1
3
12
``` enum SampleEnum {} let type: Any.Type = SampleEnum.self String(reflecting: type) // this gives: AppName.SampleEnum ``` @jckarter is this kind of enum metadata (especially type name) ABI-stable? I can see a lot of "debug" naming behind the stage.
1
I had a really great time slicing the byte buffers together with @keno42 at @SwiftServerConf.
1
2
1
26
The workshop with @amlug at @SwiftServerConf just got really serious.
5
Every developer sometimes needs to stand on one’s head. Watching all the awesome presentations from @mobiconf will make you swifty. #mobiconf2019
2
1
1
20
Replying to @Valzevul
@Valzevul thanks for this eye-opening presentation about shifted paradigm of watchOS ⌚️ development. #mobiconf2019
1
1
You can fighting the global warming with one simple Xcode trick. 🌱 Not using Swift Metadata? Set `SWIFT_REFLECTION_METADATA_LEVEL = none` for Release configuration. Doing so could save megabytes on your binary size. 🗜
4
5
1
34
UPDATE: This setting could cause crashes when used in a SwiftUI app. I stopped using it in my apps. Also mind that this could change behavior or reflection-dependent stuff (e.g. type string interpolation).
1
8
Looks like Apple looks at my radars from time to time 😅 openradar.appspot.com/362439… fixed ❤️🍏
5
During my talk at #SwiftFest I told that this is a good idea to enable `DEPLOYMENT_POSTPROCESSING`, but I didn't know that postprocessing (or at least full binary stripping) is performed during the Archive anyway. Sorry for that false information. 😓
1
2
Regarding `SWIFT_REFLECTION_METADATA_LEVEL` – tweaking this property is still a good idea. 😋
2
Replying to @NamrataCodes
@NamrataCodes explained not only how to start with #arkit, but also how to lift an AR experience to the top level. 💎 I will definitely watch her #swiftfest presentation again before even starting an AR project.
1
6
Want to know iOS accessibility in depth? Definitely check @dadederk #swiftfest presentation – he showed a lot of interesting accessibility features I was not even aware of.
4
6
Replying to @_LeenaM
@_LeenaM gave an amazing presentation on testing accessibility during the #SwiftFest conf. Her testing approach helped me realize how much improvement my apps need 😢 Fortunately she also gave a lot of handy tips on how to improve that 😃 Can’t wait to apply them!
1
4
Replying to @giorgionatili
@giorgionatili @theSwiftFest thanks for organizing such a wonderful event. It was amazing from the audience as well from the stage 🕺🏽 #swiftfest
1
8
📡 `Text.lineLimit(x)` gives `x-1` limit openradar.appspot.com/613569…
1
1
1