Jessy Catterwaul
@jessymeow.bsky.social
My stuff: catterwaul.com
My favorite thing on Bluesky: @possumeveryhour.io
My favorite thing on Bluesky: @possumeveryhour.io
It seems to me that your `Catching` protocol is better-represented as a union type. Thoughts?
October 26, 2025 at 6:07 PM
It seems to me that your `Catching` protocol is better-represented as a union type. Thoughts?
Roll Player Adventures does use this arrangement, but only on multicolored (familiar 🐅) dice.
I still don't think I've seen this arrangement for 5:
⬜️⚫️⬜️
⚫️⚫️⚫️
⬜️⚫️⬜️
Using the negative space of 4, for 5, like this, might have helped 6 not be so unruly.
(Standard 5-quincunx is fine w/me in isolation.)
I still don't think I've seen this arrangement for 5:
⬜️⚫️⬜️
⚫️⚫️⚫️
⬜️⚫️⬜️
Using the negative space of 4, for 5, like this, might have helped 6 not be so unruly.
(Standard 5-quincunx is fine w/me in isolation.)
October 9, 2025 at 5:57 PM
Roll Player Adventures does use this arrangement, but only on multicolored (familiar 🐅) dice.
I still don't think I've seen this arrangement for 5:
⬜️⚫️⬜️
⚫️⚫️⚫️
⬜️⚫️⬜️
Using the negative space of 4, for 5, like this, might have helped 6 not be so unruly.
(Standard 5-quincunx is fine w/me in isolation.)
I still don't think I've seen this arrangement for 5:
⬜️⚫️⬜️
⚫️⚫️⚫️
⬜️⚫️⬜️
Using the negative space of 4, for 5, like this, might have helped 6 not be so unruly.
(Standard 5-quincunx is fine w/me in isolation.)
There's a lot of mention of `===` in forums.swift.org/t/se-0261-id..., but it's not in the standard library.
The `===` we've always had doesn't require arguments of matching type, so I don't know that it would feel consistent. (github.com/swiftlang/sw...)
The `===` we've always had doesn't require arguments of matching type, so I don't know that it would feel consistent. (github.com/swiftlang/sw...)
July 25, 2025 at 10:51 AM
There's a lot of mention of `===` in forums.swift.org/t/se-0261-id..., but it's not in the standard library.
The `===` we've always had doesn't require arguments of matching type, so I don't know that it would feel consistent. (github.com/swiftlang/sw...)
The `===` we've always had doesn't require arguments of matching type, so I don't know that it would feel consistent. (github.com/swiftlang/sw...)
As cool as pack iteration is, you don't actually need it for your outer loop.
P.S. I hate the inability of multiple where clauses to get auto-formatted! ☹️ This is what I want it to look like:
P.S. I hate the inability of multiple where clauses to get auto-formatted! ☹️ This is what I want it to look like:
June 23, 2025 at 2:16 AM
As cool as pack iteration is, you don't actually need it for your outer loop.
P.S. I hate the inability of multiple where clauses to get auto-formatted! ☹️ This is what I want it to look like:
P.S. I hate the inability of multiple where clauses to get auto-formatted! ☹️ This is what I want it to look like:
I am excited about developing for Vision hardware as a 3D monitor for use in tandem with macOS. "VVVDC25" brought that: developer.apple.com/documentatio...
The documentation is bad, though, not mentioning what Macs support this. 😖 I had to run the beta to figure out my M1 Pro MacBook Pro does. 🥳
The documentation is bad, though, not mentioning what Macs support this. 😖 I had to run the beta to figure out my M1 Pro MacBook Pro does. 🥳
June 13, 2025 at 8:46 PM
I am excited about developing for Vision hardware as a 3D monitor for use in tandem with macOS. "VVVDC25" brought that: developer.apple.com/documentatio...
The documentation is bad, though, not mentioning what Macs support this. 😖 I had to run the beta to figure out my M1 Pro MacBook Pro does. 🥳
The documentation is bad, though, not mentioning what Macs support this. 😖 I had to run the beta to figure out my M1 Pro MacBook Pro does. 🥳
I noticed a bunch of petals on the deck, and looked up. We do have some flowers—at least for a moment! The chipmunks don't live up here, but the squirrels do. I hope they enjoy the seasonal decorations!
June 8, 2025 at 7:31 PM
I noticed a bunch of petals on the deck, and looked up. We do have some flowers—at least for a moment! The chipmunks don't live up here, but the squirrels do. I hope they enjoy the seasonal decorations!
We've got something like that around here, as well! 😹
(The chipmunk drops off, after early spring, but happily never reaches zero.)
(The chipmunk drops off, after early spring, but happily never reaches zero.)
June 6, 2025 at 11:09 PM
We've got something like that around here, as well! 😹
(The chipmunk drops off, after early spring, but happily never reaches zero.)
(The chipmunk drops off, after early spring, but happily never reaches zero.)
Sorry, we don't have much in the way of flowers. The best I can do is chipmunks. 😻🐿️
I finished up yesterday with a new wood chip shipment for them to burrow in.
I finished up yesterday with a new wood chip shipment for them to burrow in.
June 6, 2025 at 8:46 PM
Sorry, we don't have much in the way of flowers. The best I can do is chipmunks. 😻🐿️
I finished up yesterday with a new wood chip shipment for them to burrow in.
I finished up yesterday with a new wood chip shipment for them to burrow in.
We just tried Hallertau for the first time tonight. It’s a keeper. Nusfjord is on the to-try list.
May 25, 2025 at 4:46 AM
We just tried Hallertau for the first time tonight. It’s a keeper. Nusfjord is on the to-try list.
@grodld.bsky.social This one is a holdover from C++. The terrible auto-indentation unfortunately makes its way into Metal as well. 😭
April 25, 2025 at 12:47 PM
@grodld.bsky.social This one is a holdover from C++. The terrible auto-indentation unfortunately makes its way into Metal as well. 😭
Also, Dot offers "Note", which doesn't show in the graph. (I don't know if any other nodes have this.)
Inconsistently, you need to *option*-click to get another line there.
And the text box doesn't stretch vertically.
And you have to click in the note to see more lines.
😑
Inconsistently, you need to *option*-click to get another line there.
And the text box doesn't stretch vertically.
And you have to click in the note to see more lines.
😑
April 14, 2025 at 6:30 PM
Also, Dot offers "Note", which doesn't show in the graph. (I don't know if any other nodes have this.)
Inconsistently, you need to *option*-click to get another line there.
And the text box doesn't stretch vertically.
And you have to click in the note to see more lines.
😑
Inconsistently, you need to *option*-click to get another line there.
And the text box doesn't stretch vertically.
And you have to click in the note to see more lines.
😑
I think the only solution for the latter is to use "Group". It's not great—I'm a DocC user and miss that a lot in RCP—but I think it's at the level of what you're asking.
April 14, 2025 at 6:24 PM
I think the only solution for the latter is to use "Group". It's not great—I'm a DocC user and miss that a lot in RCP—but I think it's at the level of what you're asking.
From our experience so far, Highland Brewing in Asheville, NC does the course thing best, but they're not a farm, likely due to the lack of flatness.
udisc.com/courses/high...
highlandbrewing.com
udisc.com/courses/high...
highlandbrewing.com
April 6, 2025 at 4:51 AM
From our experience so far, Highland Brewing in Asheville, NC does the course thing best, but they're not a farm, likely due to the lack of flatness.
udisc.com/courses/high...
highlandbrewing.com
udisc.com/courses/high...
highlandbrewing.com
Something like that is probably going to make more sense than the only fix I think exists (someone mentioned this today): creating your own DisclosureGroupStyle. I don't think there's any way to amend AutomaticDisclosureGroupStyle like this. 😾
I'm adding a PR with this visualization to your repo.
I'm adding a PR with this visualization to your repo.
March 30, 2025 at 12:41 AM
Something like that is probably going to make more sense than the only fix I think exists (someone mentioned this today): creating your own DisclosureGroupStyle. I don't think there's any way to amend AutomaticDisclosureGroupStyle like this. 😾
I'm adding a PR with this visualization to your repo.
I'm adding a PR with this visualization to your repo.
Decoding, I think I get? But I'm not sure on the encoding, because based on this decoding algorithm, multiple values can encode to the same alien number. 🛸
March 28, 2025 at 3:45 PM
Decoding, I think I get? But I'm not sure on the encoding, because based on this decoding algorithm, multiple values can encode to the same alien number. 🛸
I like to combine the two approaches, for organizational namespacing purposes.
March 23, 2025 at 6:12 PM
I like to combine the two approaches, for organizational namespacing purposes.
So far, yes! But I've found `Result.zip` to be useful in the past, and Task is much like an asynchronous get-only Result. So I've just wondered how best to translate the idea for when it will inevitably be useful.
(I've used `Optional.zip`, their antecedent, in non-pack form, since the early years.)
(I've used `Optional.zip`, their antecedent, in non-pack form, since the early years.)
March 15, 2025 at 9:50 PM
So far, yes! But I've found `Result.zip` to be useful in the past, and Task is much like an asynchronous get-only Result. So I've just wondered how best to translate the idea for when it will inevitably be useful.
(I've used `Optional.zip`, their antecedent, in non-pack form, since the early years.)
(I've used `Optional.zip`, their antecedent, in non-pack form, since the early years.)
What's your go-to for heterogeneous task groups? I'd love something more reusable than e.g. www.hackingwithswift.com/quick-start/....
Is a good, more robust, properly-canceling form of this naïve zipping approach, possible?
Is a good, more robust, properly-canceling form of this naïve zipping approach, possible?
March 15, 2025 at 6:51 AM
What's your go-to for heterogeneous task groups? I'd love something more reusable than e.g. www.hackingwithswift.com/quick-start/....
Is a good, more robust, properly-canceling form of this naïve zipping approach, possible?
Is a good, more robust, properly-canceling form of this naïve zipping approach, possible?
Letting it autocomplete "lit" is pretty good. The only current option you don't get from that is ExpressibleByStringInterpolation.
But `strl`, down, enter, is even better.
But `strl`, down, enter, is even better.
March 13, 2025 at 8:47 AM
Letting it autocomplete "lit" is pretty good. The only current option you don't get from that is ExpressibleByStringInterpolation.
But `strl`, down, enter, is even better.
But `strl`, down, enter, is even better.
Here's the simplest case. 😖
March 8, 2025 at 1:38 AM
Here's the simplest case. 😖
Here's an illustration of the required BS. I always used `do` just to create scope more in tests than anywhere else, but it's gotten a little ridiculous with Swift Testing.
March 7, 2025 at 1:53 PM
Here's an illustration of the required BS. I always used `do` just to create scope more in tests than anywhere else, but it's gotten a little ridiculous with Swift Testing.
Do you know about goshdarnifcaseletsyntax.com ?
I like it better than guard + else { continue } in the loop body.
I like it better than guard + else { continue } in the loop body.
March 3, 2025 at 10:36 PM
Do you know about goshdarnifcaseletsyntax.com ?
I like it better than guard + else { continue } in the loop body.
I like it better than guard + else { continue } in the loop body.
Yep, that's it. Here's what happens with non-opaque typing. Okey dokey! 🤷 Thanks!
March 2, 2025 at 10:50 PM
Yep, that's it. Here's what happens with non-opaque typing. Okey dokey! 🤷 Thanks!