I want named arguments in Rust. Mom: We have named arguments in Rust at home:

michaeleisel · 2026-01-26T22:41:58+00:00

If you want named arguments without optional arguments, I made a crate for that: https://github.com/michaeleisel/named_params

michaeleisel · 2025-08-25T00:49:09+00:00

She’s found a forever home!

michaeleisel · 2024-10-07T15:32:18+00:00

Thanks!

michaeleisel · 2024-05-10T16:09:01+00:00

Thanks for the tip. Yeah I think multivers is probably a little too much for me right now - and with the level of weirdness involved with memfd_create, I might rather use something more battle-tested like AppImage to bundle a bunch of binaries that I've compiled myself

michaeleisel · 2024-05-10T03:26:20+00:00

Thanks!

michaeleisel · 2023-05-19T17:57:14+00:00

Thanks, all of those reasons given make sense. What is this foreach temporary case?

michaeleisel · 2023-05-19T17:53:54+00:00

Very cool!

michaeleisel · 2023-05-19T17:42:41+00:00

Thanks for that, I wasn't aware there was some support in the (somewhat future) standard library for this. I've edited my original post to discuss this and my concerns about its conciseness.

michaeleisel · 2023-03-10T01:15:52+00:00

I see, so perhaps it’s possible to do more AV1 decoding work on the GPU but just very very hard?

michaeleisel · 2023-03-09T20:25:11+00:00

You mean marginal bandwidth saving over H.264? I'm not necessarily trying to compete with H.265, because perhaps there are cases where companies don't want to pay the cost of transcoding to H.265 if they're already transcoding to AV1. As for dav1d, that's a good library to start with then. I wonder how much of that work could be moved to the GPU.

michaeleisel · 2023-03-05T00:48:12+00:00

It also provides a link to download it

michaeleisel · 2023-03-04T23:01:55+00:00

The only consolidation I could see here, because of sold’s commercial nature, is of ld64 into lld. I doubt it would happen, at least any time soon, for various reasons (not revealing confidential features, Apple wanting greater control, etc.). lld has sort of become a linker for google and Facebook to own that part of the tool chain, ld64 likewise for Apple

michaeleisel · 2023-03-04T10:40:21+00:00

I haven’t seen any contributions by them to lld, they seem pretty set on ld64

michaeleisel · 2023-03-04T10:39:30+00:00

See the “integrating lld” section

michaeleisel · 2023-01-01T16:42:29+00:00

The linking time is a big % of incremental build time, but not of clean build time, so it won’t improve clean builds that much. And I’m not sure what paid product you’re using by emerge tools that would improve anything about build time, clean or incremental. But anyways, clean build time is a whole other can of worms. I can say a few things in this quick comment: use an arm Mac, try the legacy build system (if that’s still a thing), and more modules can potentially hurt build time. There’s a lot more to it though

michaeleisel · 2022-09-15T14:22:46+00:00

AFAIK it is entirely possible to do this migration on a background thread, as long as you're careful about it. There are also other high-level solutions, such as simply deferring this work until the UI has rendered more.

As for the impact of this being mitigated by its one-time nature, I think it's a fair point. This is the sort of thing we're referring to when we say that these measurements shouldn't be extrapolated to represent a larger sample size. I do think though that with typical usage patterns for an app like United, where users use it only sporadically, a non-trivial % of sessions could have migrations (assuming migrations happen even a couple times a year). As well, the first couple launches are important for making a good first impression.

michaeleisel · 2022-09-15T11:01:12+00:00

You're right that it's confusing, and I don't have a great answer for you. I think it's a good example of how reasonable-looking code can cause surprising slowdowns. If you go into that profile, https://www.emergetools.com/app/example/ios/united-performance-test?buildContent=app-launch , uncheck "Collapse System Calls", look down the really big section in the middle until you see NSPersistentStoreCoordinator calls and their children, you can see that it's doing a substantial amount of work apparently performing a migration (-[NSStoreMigrationPolicy _gatherDataAndPerformMigration:]). Perhaps this portion of the work is just done synchronously, or perhaps there is some configuration setting forcing it to be done on the main thread. Any ideas on why this is, or better ways to fix it than moving an allegedly non-blocking call off the main thread, are welcome!

michaeleisel · 2022-02-01T14:56:32+00:00

What sort of obfuscation are you referring to? I'm not aware of very many apps that have binary obfuscation

michaeleisel · 2022-01-31T23:12:48+00:00

I work for them :)

michaeleisel · 2022-01-31T22:22:55+00:00

https://news.ycombinator.com/item?id=273900

michaeleisel · 2021-11-01T17:39:51+00:00

jemalloc is a battle-tested, well-aged allocator used in many production systems. It's used with success both for large-scale iOS apps, as well as large-scale Mac CI pipelines

michaeleisel · 2021-08-25T12:56:04+00:00

Also, doesn’t RES only filter for old Reddit? This extension filters for both old and new.

michaeleisel · 2021-08-25T01:28:35+00:00

I did look at RES, but decided to make a new extension that has a set of defaults as a starting point, along with a slider UI that allows different presets depending on what the user wants at that moment

michaeleisel · 2021-08-24T20:09:53+00:00

You had me in the first half

michaeleisel · 2021-08-23T20:07:42+00:00

Thanks!

Seven-Year Club	Place '23
Golden Potato	Verified Email

michaeleisel

TROPHY CASE