@ericjmorey @wargreymon
Physical access to memory is necessary for embed language library calls ?
Some other language is doing that for languages that sport such functionality.

@sukhmel @0x0
Reference counters, the associated libraries I mean, tend to be habitual data leak vectors?

@sukhmel @0x0
Reference counters, the associated libraries in mean, tend to be habitual data leak victors?

Permanently Deleted

@BB_C @lysdexic
If you have C as a foundation.
Presentation/Session layer frameworks have defined memory management as meaning "how much memory do you have...?"

@Ephera @AlexKochetkova
Binaries running as helpers?
Sleeping trace processes?
Seems like a lot of overhead for a system language?

@nickwitha_k @towerful

Write a driver or i/o for an mcu?
Unless most is already done i don't see rust at present able to make something scalable.
And that's not about rust it's about mcu's.....
I could be wrong though.

But it's supported so some cool learning can go on.....

@FizzyOrange
I haven't kept up with the points lately.
But over the years there have been many Discussions about the handling of pointers which should be seen as just another variable.
Mainly in languages develped after C.

@lysdexic @AbelianGrape

I don't think so.
And you never answered the question.

@FizzyOrange @Kissaki

Don't null reference languages often allow that reference to be redefined? Even if just to redefine the return type?