Posts by porglezomp@mastodon.social
 (DIR) Post #B4ZE0bel9XniHhle7M by porglezomp@mastodon.social
       0 likes, 0 repeats
       
       @whitequark i can imagine a few cases where reformatting a code could change behavior (mostly related to language constructs that capture source locations) so I think I would be willing to accept as low as 99.99%
       
 (DIR) Post #B4av2O1BJz2NkhJIq8 by porglezomp@mastodon.social
       1 likes, 0 repeats
       
       Xcode 26.4 is out, and it contains one nice small thing for Clang users: the Apple Clang version numbers finally correspond to the upstream Clang versions. (Apple Clang 21 is based on the Clang 21 release branch.)
       
 (DIR) Post #B4av2PRo0TvcBYm4ye by porglezomp@mastodon.social
       0 likes, 0 repeats
       
       Previously it was like “Apple Clang 17 is based on the Clang 19 release branch” because the version numbers matched the Xcode version number.
       
 (DIR) Post #B4cWLVVnZgLlxSZVzs by porglezomp@mastodon.social
       0 likes, 1 repeats
       
       @seanmiddleditch LLDB does have declarative summaries https://lldb.llvm.org/use/variable.html (which can be embedded in the binary at least in Apple LLDB, I can’t tell if that got upstreamed) and I don’t remember the current status but Adrian was working on expanding this for more complex functionality: https://discourse.llvm.org/t/a-bytecode-for-lldb-data-formatters/82696
       
 (DIR) Post #B6PPV0HjOi6us97nyS by porglezomp@mastodon.social
       0 likes, 0 repeats
       
       @ariadne yeah I like the zig project and I respect their engineering but their language is not for me
       
 (DIR) Post #B9ZieYrSKO0lP0cd3w by porglezomp@mastodon.social
       0 likes, 0 repeats
       
       @ariadne try to bring the analysis to it