If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
They can drop them in C as well. It is as easy as making the decision to drop support of legacy compilers and platforms.
I am not sure what they mean by unit tests to core functions. Can't this be achieved in C? Though is an important enough reason so as to rewrite the whole thing in another language?
LOL. This is the real reason for why they are doing it.
Please, re-read the article. He never said that Rust has a bigger ecosystem than C/C++, he said it's rapidly GROWING.
Projects like this are as much about testing the capabilities of the Rust language as anything. They want to know if they can hit any cases where Rust is deficient in a variety of real-world applications. With a view to improving Rust by fixing any deficiencies found.
Wow, people on this forum really likes to tell people what they should or shouldn't spend their own time on. I take it your productiveness are superior and you only do stuff that will benefit society, while not doing anything that will satisfy only yourselves.
Porting to Rust gives us lots of opportunities. We can leverage the rapidly-growing crate ecosystem.
There is not bigger ecosystem than C/C++.
We can drop support legacy compilers and platforms (looking at you, MS-DOS).
They can drop them in C as well. It is as easy as making the decision to drop support of legacy compilers and platforms.
We can add docstrings and unit tests to core functions that aren’t exposed to elisp.
I am not sure what they mean by unit tests to core functions. Can't this be achieved in C? Though is an important enough reason so as to rewrite the whole thing in another language?
It’s also a ton of fun.
LOL. This is the real reason for why they are doing it.
Leave a comment: