amos
banner
fasterthanlime.hachyderm.io.ap.brid.gy
amos
@fasterthanlime.hachyderm.io.ap.brid.gy
hi, I'm amos! 🍃 they/them 🫐 open-source witch & maker of snappy videos and articles at https://bearcove.eu ✨ be kind, be curious

🌉 bridged from ⁂ https://hachyderm.io/@fasterthanlime, follow @ap.brid.gy to interact
@larsmb woof
November 30, 2025 at 8:28 PM
November 30, 2025 at 6:20 PM
term update: I'm back to iTerm2 for the time being because... tmux integration???

I had never taken the time to set it up properly and it's glorious.
November 30, 2025 at 1:46 PM
Could you send (previous toot) to my past self verbatim? 100% yeah. That's how I know. Thanks for coming to my ted talk.
November 30, 2025 at 1:40 PM
See that's what I want.

I mean, I want more. But it's a good start.
November 29, 2025 at 6:47 PM
@whitequark it can (and will) get even better — the showcase isn't showing half of what we can do
November 29, 2025 at 3:28 AM
@whitequark it's definitely what I intended, months ago, when my brain was still fresh. I remembered vaguely that storage would be annoying, and.. today I just went in a completely different direction lol
November 29, 2025 at 12:35 AM
@whitequark this is.. so much better on so many levels
1) everything validated at compile time
2) better diagnostics (arbitrarily better, if you want to bring a proc macro welcome to the party)
3) no heap allocation required for the 'parsed form' of attribute values — it's now just a &'static […]
Original post on hachyderm.io
hachyderm.io
November 29, 2025 at 12:30 AM
@whitequark ...yep. thanks!!!!
November 29, 2025 at 12:26 AM
@ljmc please, call me BIG
November 29, 2025 at 12:14 AM
@whitequark likely — I will try it out and report back.
November 28, 2025 at 11:43 PM
@whitequark oh no it could just be a decl macro

why did I not think of this

I'm an idiot
November 28, 2025 at 11:40 PM
@whitequark hmph but then everyone has to ship a proc macro which suuuuuucks
November 28, 2025 at 11:38 PM
@whitequark fphfmhmmhhmhmh.
November 28, 2025 at 11:36 PM
@whitequark or, wait, you're saying to produce a macro invocation
November 28, 2025 at 11:36 PM
@whitequark this only works if `facet-macros` knows about third_party_crate and imports its proc macro as a function which it can then run
November 28, 2025 at 11:36 PM
@whitequark oh for sure, but the problem is... pluggability. it's for facet attributes contributed by third-party crates. I've already found a bunch of tricks, but the actual parsing of the attribute value still happens at runtime for now
November 28, 2025 at 11:35 PM