Fil-C... The Future Of Slackware?

fu11m00n

I am the maintainer of... "the fu11m00n project" (on Sourceforge).
It's based on Slackware (and Porteus).
Recently... my project was taken off the DistroWatch waiting list and is now ranked.
My project focus is a "suckless.org" deprecation of the GNU ecosystem.
I made a thread sometime ago about creating a Aarch64 Porteus.
Unfortunately (@ least for the moment) I am abandoning that effort.
The reason is a YouTube (Lunduke) video with the creator of Fil-C (memory safe C).
Currently... Fil-C is x86_64 only.
It's creator has taken projects like... Musl and Coreutils and rewote them in Fil-C.
I'm big on security... but I'm on the fence about going all in.
If I go down that rabbit hole it means (@ least for now) shelving Aarch64.
Originally... I was all in on Rust rewrites but now I'm considering abandoning that for Fil-C.
So... to Fil-C or not Fil-C (that is the question)?
Is Fil-C the future of Slackware or just a unicorn?
What are the pros... cons (and mitigations)?
If Fil-C is a winner it means memory safety for my project without the convoluted bloat of Rust.