profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/keith/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Keith Smiley keith Lyft San Francisco, CA https://smileykeith.com iOS @Lyft

christoomey/vim-tmux-navigator 3388

Seamless navigation between tmux panes and vim splits

CocoaPods/Rome 665

Makes it easy to build a list of frameworks.

bazelbuild/tulsi 385

An Xcode Project Generator For Bazel

bazelbuild/rules_apple 230

Bazel rules to build apps for Apple platforms.

bazelbuild/rules_swift 162

Bazel rules to build Swift on Apple and Linux platforms

bazel-ios/rules_ios 105

Bazel rules for building iOS applications and frameworks

kattrali/webkitten 35

A command-driven web browser toolkit inspired by luakit and Vim.

bazelbuild/apple_support 23

Apple support for Bazel rules

keith/color-builder 14

base16 builder with solarized templates

keith/cocoapods-foundation-headers 12

A CocoaPods plugin to stop polluting your project with UIKit/Cocoa imports

startedSysinternals/ProcMon-for-Linux

started time in 22 minutes

issue closedmichaeleisel/zld

Cannot build from source

I'm trying to build from source the project following the instructions in the README file but I have several issues.

Building from source
Install Xcode 12.2+ and run sudo xcode-select -s <path to Xcode>
Install cmake
Checkout the latest release of zld from master
Run make clean && make

I attached in the following gist the log files. It seems that running the command make clean && make the compilation fails for some missing dependency library. If I run make again without cleaning the compilation makes some steps again but fails without finding corecrypto dependencies (that gets deleted on the clean, is it correct?).

https://gist.github.com/lechuckcaptain/aafdc3877caa2fb8a7f10454af4f4336

I also tried to reset the repo, and run only the make command without any clean. I gets at first the same error of missing some dependency library, but on the second make I get a different error this time. Please find some info in this second gist:

https://gist.github.com/lechuckcaptain/49624151b8974f88576b6e661c873418

Do you have any idea what could be the issue?

closed time in 32 minutes

lechuckcaptain

issue commentnicklockwood/SwiftFormat

Wrong formatting of multiline guard entries

@danyf90 "broken" is a bit subjective here. Those are both reasonable ways for that code to be formatted. I agree that it's not how Xcode does it (at least as-of v12, when Apple changed how everything was indented).

danyf90

comment created time in an hour

startedpenpot/penpot

started time in an hour

startedgo-git/go-git

started time in an hour

pull request commentapple/swift

Fix an assert in exclusivity diagnostics when inouts escape.

@swift-ci smoke test macOS

atrick

comment created time in an hour

pull request commentapple/swift

Fix an assert in exclusivity diagnostics when inouts escape.

3rd spurious error: Driver/Dependencies/only-skip-once.swift

atrick

comment created time in an hour

pull request commentapple/swift

Initial clean-up pass for structured concurrency doc comments

Oh sorry I missed the updates! Checking now :) Please ping me on chat if I miss something for a few days :)

amartini51

comment created time in an hour

startedlief-project/LIEF

started time in an hour

Pull request review commentapple/swift

Initial clean-up pass for structured concurrency doc comments

 public func withUnsafeCurrentTask<T>(body: (UnsafeCurrentTask?) throws -> T) ret   return try body(UnsafeCurrentTask(_task)) } -/// An *unsafe* 'current' task handle.+/// An unsafe task handle for the current task. ///-/// An `UnsafeCurrentTask` should not be stored for "later" access.+/// To get an instance of `UnsafeCurrentTask` for the current task,+/// call the `withUnsafeCurrentTask(body:)` method.+/// Don't try to store an unsafe task handle

storing it is actively unsafe and would lead to undefined behavior, so the stronger wording would be good hm

amartini51

comment created time in an hour

PR opened bazelbuild/buildtools

renamed attribute in buildifier rule: _buildifier -> buildifier

Allow users to specify their own buildifier binary in the buildifier rule. For example, users can use a pre-build binary that can be download from the github release page. Fixes #974

+7 -7

0 comment

1 changed file

pr created time in an hour

Pull request review commentapple/swift

Initial clean-up pass for structured concurrency doc comments

 extension Task {   } } -/// Calls the given closure with the with the "current" task in which this-/// function was invoked.+/// Calls a closure with an unsafe handle to current task.+///+/// If you call this function from the body of an asynchronous function,+/// the unsafe task handle passed to the closure is always be non-nil+/// because an asynchronous function always runs in the context of a task.+/// However if you call this function from the body of a synchronous function,+/// the unsafe task handle is `nil`

it would be nil then -- if the entire callstack is outside of swift concurrency APIs

amartini51

comment created time in an hour

Pull request review commentapple/swift

Initial clean-up pass for structured concurrency doc comments

 extension Task { @available(macOS 9999, iOS 9999, watchOS 9999, tvOS 9999, *) extension Task { -  /// Explicitly suspend the current task, potentially giving up execution actor-  /// of current actor/task, allowing other tasks to execute.+  /// Suspends the current task and allows other tasks to execute.   ///-  /// This is not a perfect cure for starvation;-  /// if the task is the highest-priority task in the system, it might go-  /// immediately back to executing.+  /// A task can voluntarily suspend itself+  /// in the middle of a long-running operation+  /// that doesn't contain any suspension points,+  /// to let other tasks run for a while+  /// before execution returns back to this task.+  ///+  /// Note that if this task is the highest-priority task in the system,+  /// the executor immediately resumes execution of the same task.+  /// As such,+  /// this method isn't necessarily a way to avoid resource starvation.

I see, that's a new technique to me but sounds fine I guess , thanks for explaining

amartini51

comment created time in an hour

startedsatya164/react-simple-code-editor

started time in an hour

startedmunificent/craftinginterpreters

started time in an hour

pull request commentapple/swift

[DON'T MERGE] TEST

https://github.com/apple/llvm-project/pull/2930 @swift-ci test Windows

shahmishal

comment created time in an hour

pull request commentapple/swift

Async let family

@swift-ci please test

DougGregor

comment created time in 2 hours

PR opened apple/swift

Async let family r5.5

Introduce the "family" of names around async let:

  • async let for child task variables
  • TaskGroup.async for initiating async work as a child task
+116 -89

0 comment

19 changed files

pr created time in 2 hours

pull request commentapple/swift

Reinstate "async let", with "spawn let" as an alias.

@swift-ci please smoke test

DougGregor

comment created time in 2 hours

PR opened apple/swift

Reinstate "async let", with "spawn let" as an alias.
+128 -101

0 comment

21 changed files

pr created time in 2 hours

pull request commentapple/swift

libswift: Start implementing SIL optimizations in Swift

@swift-ci smoke test

eeckstein

comment created time in 2 hours

startedpbatard/rufus

started time in 2 hours

issue commentyonaskolb/XcodeGen

xcodegen command gives spec validations error

@DavidWoohyunLee I had the same problem when using "Devel Archive" and "Devel Run" in my configuration names.

It appears that the definition of "Config Variant" assumes that you always include the words "Debug" and "Release" in your config name, right after the "variant" name and not before.

In my case I had to switch "Devel Run" to "Devel Debug" and "Devel Archive" to "Devel Release" and everything started to work again.

From documentation:

This generates a scheme for each entry, using configs that contain the name with debug and release variants. This is useful for having different environment schemes.

I guess it's assumed that "debug" and "release" should be placed at the end of config name, not at start.

DavidWoohyunLee

comment created time in 2 hours

startedlief-project/LIEF

started time in 2 hours

issue commentnicklockwood/SwiftFormat

Wrong formatting of multiline guard entries

Just noticed that it is also broken in much simpler cases like:

guard
    testArray
      .map { $0 * 2 }
      .filter { $0 == 4 }
      .isEmpty
else {
  …
}

which is wrongly reformatted as:

guard testArray .map { $0 * 2 } .filter { $0 == 4 } .isEmpty else { … }

danyf90

comment created time in 3 hours

issue commentyonaskolb/XcodeGen

Currently .xcconfig files on Xcode don't seem to follow the folder hierarchy.

@freddi-kit thanks a lot, I'll check!

Elland

comment created time in 3 hours

issue commentnicklockwood/SwiftFormat

Not seeing SwiftFormat in Xcode 12.1/Big Sur

Linking #804 for cross referencing...

ahwulf

comment created time in 3 hours

PublicEvent

pull request commentapple/swift

[Concurrency] Revert 'nonisolated let' change.

@swift-ci please test

DougGregor

comment created time in 4 hours

PR opened apple/swift

[Concurrency] Revert 'nonisolated let' change. r5.5

The change made to SE-0306 to require 'nonisolated let' is undercutting the effectiveness of the model. Revert while we work on a better solution.

+94 -68

0 comment

10 changed files

pr created time in 4 hours