f16 and f128

Great!👍🏻 What about FPU and VFP support?

this or this.

Looking to example code in the README I have to say that it is neat! ❤️‍🔥 But know what? Could be awesome to support char-literals in the parser! macro. Currently in that example str-literals used as single-char strings. I mean this for example:

num: num=<"-"? '0'-'9'+ …

Why there dash is str but not a char? Also what about escapes, unicode sequences and binary literals?

I suppose there should be something like Crang (“friend” of Shredder) without exoskeleton and covered with spikes, like your Corro.

Done!

Ok, understood, thank you.

I’m not sure is it sarcasm or that’s really not bad short description? 🤔

Trying to reduce compilation time, reconfiguring underlying cargo’ build-ctx or just riding off the context and using only build-plan and metadata by host cargo & rustc in the cargo-playdate tool.

Nope. This little neat feature mainly is just necessary part of bigger one - const-generics with const bounds.

🙀

If I understand you right, I mean just star button on that repo. Thank you 😊

Thanks! ❤️‍🔥

I just don’t care, I’m only 40 years old, it’s a kid’s age.

Did author knows about difference between static and dynamic dispatch? 🤦🏻‍♂️

Okay, just take a look at code. https://github.com/aeharding/voyager

Just one question - where it is native? Are you pretty sure?

Unison stores code in a database.

🫣🤨

It’s to teach AI more properly?

I love ligatures and Fira Code (retina) is the best and absolutely comfortable for me.

Seems to my mistake. You question is about CI/CD services that supports Pijul. So yes, almost zero. But it’s like ouroboros. Just use pijul more then git and talk about it, and services will support it soon.