Skip to content

Instantly share code, notes, and snippets.


Ilya Kulakov Kentzo

View GitHub Profile
View AoC22.pdf
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

The benchmark measures and compares execution time and peak memory consumption of the current and new commonpath methods.

Measurement is performed using batches of 1000 paths. Each batch contains paths generated with the following variables:

  1. Length of each path part (range(16, 65, 16))
  2. Number of parts (range(4, 17, 4))
  3. Number of common parts (range(parts_count + 1))

The batch is then split into chunks of equal size such that paths in each following chunk reduce the number of common parts so far by 1 up to the selected number [3], e.g. if the selected number of common parts is 1 then the batch would be "a/b/c", "a/b/c", "a/b/d", "a/b/d", "a/c/d", "a/c/d", "a/c/d".

Each batch is tested in two permutations:

Kentzo /
Last active Oct 16, 2022
Guess file type from python on macOS, no dependencies
import contextlib
import subprocess
def file_proc():
args = [
View fpvector_from_uint64.asm
punpckldq xmm0, 0x4530000043300000
subpd xmm0, 0x4330000000000000
haddpd xmm0, xmm0
Kentzo / FB7642814
Created Mar 28, 2020
Carbon API to handle Global Hot Keys should propagate hot key events as regular KeyDown / KeyUp events if not handled
View FB7642814
Among the small subset of Carbon API that still exists and has no modern replacement is an API to register Global Hot Keys. This API works in 2 steps:
1. Install an Event Handler for GetEventDispatcherTarget() for kEventHotKeyPressed and kEventHotKeyReleased
2. Registering Hot Keys with RegisterEventHotKey for GetEventDispatcherTarget()
Once the registered key combination is pressed, custom Event Handler gets called. The handler can then either return a noErr indicating that the event was processed and does not need to be propagated further, return eventNotHandledErr indicating that event should be propagated or any other error.
This issue with this API is that once a keyboard event is recognized as a Hot Key it's not put back onto event queues by macOS as a regular KeyDown / KeyUp event. Not even when all installed event handlers return eventNotHandledErr.
The workaround is to construct the appropriate KeyDown / KeyUp and manually post it on an event queue. This, unfortunately, requires the app to have t
View _0_NoReentryScope.m
void _NoReentryScopeEnter(BOOL *aVar)
if (*aVar)
[NSException raise:NSInternalInconsistencyException format:@"the method is not reentrable"];
*aVar = YES;
void _NoReentryScopeLeave(BOOL **aVar)
View final_attempt.m
@interface SRRecorderControlStyle: NSObject
// NS_SWIFT_NAME(RecorderControlStyle.Components) also works!
@interface SRRecorderControlStyleComponents: NSObject
typedef NS_ENUM(NSUInteger, SRRecorderControlStyleComponentsAppearance)
View apple.swift
var sandwich: Sandwich?
var preferences: Sandwich.Preferences?
var breadType: Sandwich.Preferences.BreadType?
View apple.m
@interface Sandwich: NSObject
@interface SandwichPreferences: NSObject
typedef NS_ENUM(NSInteger, SandwichBreadType) {
} NS_SWIFT_NAME(SandwichPreferences.BreadType);
View first_attempt.m
@interface SRRecorderControlStyle: NSObject
@interface SRRecorderControlStyleComponents: NSObject
typedef NS_ENUM(NSUInteger, SRRecorderControlStyleComponentsAppearance)
{} NS_SWIFT_NAME(RecorderControlStyle.Components.Appearance);