sure, maybe, but performance doesn’t matter for deciding if a language is memory-safe or not. And C++ isn’t memory-safe by any commonly used interpretation of that word.
You may of course decide that the downsides of memory-safety aren’t worth it for your use-case, that is a separate issue
I agree that experienced users can write code that leaks less than in C, leaving aside the bottomless pit of despair that is undefined behaviour. But the the language isn’t memory safe, it doesn’t even prevent you from returning a reference to a local or helpnwitg iterator invalidation. you don’t have to jump through any hoops to enable making that mistake.
well, its possible to check if a rust equivalent would be riddled with raw pointers: just check the Servo code base.
personally I think its a good thing to have another browser implementation, regardless of specific choices they make about language or license
that is not done in the Netherlands. For cyclists you just point in the direction you’re going with the arm closest to that direction.This is taught to children at a young age.
For driving a car I was never taught hand signals, I suspect that if you drive while your lights aren’t working, you’ll get a fine if caught. Wikipedia says that when driving oldtimers, which often don’t have a cab, you just point in the direction you’re turning, same as on a bike.
it works great on desktop using mouse too
my problem is that from any node there are two possible lines to an edgezand I’m never sure which is the correct one
Which language would you say is not memory safe then? Is there any serious language out there where you should expect memory issues if you don’t make any mistakes?