Put my images now in a #Flickr account and sorted them in different albums. Check them out for #plants, #birds, #macros and more
. All #ccbynbsa licensed for free use in non-commercial context.

Explore Plant Journeys’s 39 photos on Flickr!
non evaluated cpp template (lisp style)
One more proof by construction that we can improve derivation in #scala with #macros:
https://github.com/nguyenyou implemented sanely automatic derivation for Circe, and got some really nice numbers.
Meet #Rust + #DependencyInjection #MacroCrimes:
Supercharge Rust functions with implicit arguments using CGP v0.7.0
https://contextgeneric.dev/blog/v0.7.0-release/
Absolutely mind-blowing stuff! 🤯
I think this can be very useful for e.g. #UI libraries - really reminds me of #Vue's provide/inject mechanism:
https://vuejs.org/guide/components/provide-inject.html#provide-inject

CGP v0.7.0 has been released, bringing a major expansion to the CGP macro toolkit. The centerpiece of this release is a suite of new annotations — #[cgpfn], #[implicit], #[uses], #[extend], #[useprovider], and #[use_type] — that let you write context-generic code in plain function syntax with dramatically less boilerplate than before.
Last week I went out for a Friday night beer with friends, and left Claude running. After recent batches of improvements I hoped that Hearth was finally at the stage when I would be able to write a whole type class derivation with no bugs in my macro utilities.
I was drinking beer and approving the runs on the phone (via Happy) xD What I saw was really encouraging. How encouraging?
This is what I have one week later:
https://github.com/MateuszKubuszok/kindlings/blob/master/FEATURE_PARITY.md
I love rust, but I always kept my distances from lifetimes and macros. I'm trying to get to know macros now. After 2 days of deepseek, Claude, doc.rust-lang.org, ... I'm looking at
`$in:pat => $out:expr`
And I still don't really understand why it matches all of the following `enums`:
```
m => O::A(m)
I::A(m) => m
I::B => O::B
```
but why "expr => pat" or any other combination does NOT work.
some new lisp https://github.com/naver/lispe
with a focus on structural pattern matching

An implementation of a full fledged Lisp interpreter with Data Structure, Pattern Programming and High level Functions with Lazy Evaluation à la Haskell. - naver/lispe