As far as i know neither work on freebsd ?
The commandAs far as i know neither work on freebsd ?
pkg search '^hare' finds the following packages that seem relevant:hare-1.1 Small C client for sending ssh login notifications to a hared server
hare-lang-0.25.2_1 Hare language build system and standard library
harec-0.25.2_1 Hare compiler written in C11
But they don't work.The commandpkg search '^hare'finds the following packages that seem relevant:
I works fine on linux ,see,To my knowledge, no Carbon compiler or language environment that actually works has been released on any platform. I think the team has stated that their very optimistic goal for the first 0.x public release is the end of 2026. At that point, the language definition itself will still be experimental, so code written in 2027 will probably have to be changed as the language and tools change. Right now, a toy development environment is public that supposedly (I haven't tried it) can run simple code, but does not support compatibility with C++ code yet.
It is possible that internally, functioning Carbon development environments exist; it is also possible that Carbon code is being used already by non-public groups. If that was true, I wouldn't know about it. And if I knew about it, I would not talk about it publicly.
I know nothing about Hare except the name.
Not me!a better C++ we all want
Please elaborate.Not me!
Note. Carbon language does not have a string class in it's library. So as current is close to useless.
![]()
ld.lld: error: undefined symbol: _COp.String.Core:Copy.Core · Issue #6509 · carbon-language/carbon-lang
Following code : var test1: str = "Hi"; carbon_toolchain-0.0.0-0.nightly.2025.12.16: carbon compile works fine. carbon link produces, ld.lld: error: undefined symbol: _COp.String.Core:Copy.Core Not...github.com
Shooting yourself in the foot is a very real incentive on "what not to do".C++ is a good language. But you are allowed to abuse it and shoot yourself in the foot. A good language should prevent this.
That is the price you pay. Being an engineer is about compromise. You can either use an unsafe language to use an unsafe library directly which is quick and elegant. Or you can use a safe language but go through bindings layers against the unsafe library.But you need ugly wrappers.
My experience has been that one can use an unsafe language, safely. You just need to be very careful and take advantage of every tool to help you.That is the price you pay. Being an engineer is about compromise. You can either use an unsafe language to use an unsafe library directly which is quick and elegant. Or you can use a safe language but go through bindings layers against the unsafe library.
You can never have both. There are only three levels:
- C - direct access (~20% safe) zero bindings
- C++ - compromise (~75% safe) optional bindings
- i.e Rust - bindings jungle (~95% safe) mandatory bindings