But standardization also matters for avoiding vendor lock-in, right? Like, Python and Javascript both have many "implementations", and those are some of the most popular languages. Python does not have an ISO…
But Safe C++ and Circle are different languages, right? And Circle is not the same as the Safe C++ proposal that was submitted, right? There are presumably differences between them, and I do not know what those…
I wonder if the guarantees could be amended, considering the reactions from the Rust community.
But the changes required are generally significantly smaller and less frequent, right?
I am trying to run Carbon in Godbolt. Printing as in the example from Carbon's Github repository, does not work. 'Print("Test");' gives a complaint about not finding 'Print'.
Did Safe C++ ever have a full, correct, fully compliant, reference implementation, or was there only (closed-source) Circle as some kind of reference implementation? Circle, as far as I know, is closed-source.
Float matching in Rust is not supported due to correctness concerns, but due to historical accidents and backwards compatibility. https://github.com/rust-lang/rust/issues/41620#issuecomment-...…
> It's not possible to port a millions line C++ code base, like Chrome, to another language so large C++ projects are stuck with objectively pretty bad language and are forced to continue to use C++ even though a better…
> If WG21 were handling Rust instead f64 would implement Ord, and people would just write unsafe blocks with no explanation in the implementation of supposedly "safe" functions. Rust's technology doesn't care but their…
Is there a compiler, maybe an online one, for Carbon, or some way to compile and run Carbon code? And if not, what are the plans for that?
But standardization also matters for avoiding vendor lock-in, right? Like, Python and Javascript both have many "implementations", and those are some of the most popular languages. Python does not have an ISO…
But Safe C++ and Circle are different languages, right? And Circle is not the same as the Safe C++ proposal that was submitted, right? There are presumably differences between them, and I do not know what those…
I wonder if the guarantees could be amended, considering the reactions from the Rust community.
But the changes required are generally significantly smaller and less frequent, right?
I am trying to run Carbon in Godbolt. Printing as in the example from Carbon's Github repository, does not work. 'Print("Test");' gives a complaint about not finding 'Print'.
Did Safe C++ ever have a full, correct, fully compliant, reference implementation, or was there only (closed-source) Circle as some kind of reference implementation? Circle, as far as I know, is closed-source.
Float matching in Rust is not supported due to correctness concerns, but due to historical accidents and backwards compatibility. https://github.com/rust-lang/rust/issues/41620#issuecomment-...…
> It's not possible to port a millions line C++ code base, like Chrome, to another language so large C++ projects are stuck with objectively pretty bad language and are forced to continue to use C++ even though a better…
> If WG21 were handling Rust instead f64 would implement Ord, and people would just write unsafe blocks with no explanation in the implementation of supposedly "safe" functions. Rust's technology doesn't care but their…
Is there a compiler, maybe an online one, for Carbon, or some way to compile and run Carbon code? And if not, what are the plans for that?