3 ms·
> you have to write your new checkable C++ instead. That was more or less where I was going. Existing code is mostly hopeless, so, maybe, a dialect that makes
by rbanffy 2y ago
> you have to write your new checkable C++ instead.
That was more or less where I was going. Existing code is mostly hopeless, so, maybe, a dialect that makes more of the developer’s intentions explicit would provide enough for more checking. I don’t have evidence that Rust’s checking is why it’s slow, but I assumed it was a good guess.
- tialaramex 2y agoI think I'd have guessed similarly, but then I read the data. I don't think a C dialect is a good idea. You want a blank slate, on which you can begin with your foundational concerns (e.g. constant time evaluation) rather than starting from C. There may be practical reasons to prefer how C spells things, the way Rust looks like a semi-colon language even though it's mostly an ML, but the core language isn't helpful.
- rbanffy 2y agoThe C dialect idea would be useful if you wanted to gradually take a code base in. You’d mark parts of it as unsafe/unchecked and new code could come in using the new constructs with a more convenient syntax.