I started developing Volt/V in the middle of developing gitly.
That's my biggest drawback. I finish 90% of the project, and jump to a different thing.
I've grown a lot since then, and I'm slowly wrapping up everything.
Look, you don't owe anybody anything, and that's fine. Just don't make promises you can't keep. If you're not going to have something done in 2 days, don't say it'll be done in 2 days. Just say "you'll get it when you get it" and that's an absolutely fine response. But promising something in hours or days and missing that deadline will lead reasonable people to take your claims with a huge grain of salt.
All I'm saying is you've made some very big claims, so now you might want to master the fine art of setting expectations or risk making people lose interest in your project when you finally release a compiler.
[1]https://news.ycombinator.com/item?id=19403747
[2]https://old.reddit.com/r/vlang/comments/b2k8j7/playground/
I no longer name dates.
Claims like C++ translation is definitely one of those 90% things that may look easy to some people until you actually try to do it.
There are literally dozens of good enough small languages, e.g.: Nim, Zig, Crystal, Pony, etc etc, and at least the first two were written by a single person for the most part.
There are many other single-author single-serving languages (used to make games for example GOOL in Crash Bandicoot etc).
Not saying this can't be vaporware, but it's not beyond comprehension.
Heck, not long ago, a guy (with some psychological issues too) made his own OS, high level language compiler (HolyC), drivers, UI, and a flight simulator in assembler and HolyC, all working too (TempleOS).
I'd be ok with V though, even if it didn't do C++ translation (or even C translation at all).
Just a fast building, Algol-style syntax language, with the basic language features mentioned.