Microsoft: Rust Is the Industry’s ‘Best Chance’ at Safe Systems Programming

Re:Microsoft: Rust Is the Industry’s ‘Best Chance’ at Safe S... by bob1029 on Saturday June 13, 2020 @03:11PM (#23511855)

I think having a mode where LOH allocations are treated as a runtime exception (i.e. with a helpful exception message pointing to the offending object type) could help to guide developers down this path really well. Something like:

"LOH allocation detected for object 'MyNamespace.MyObject'. Attempted allocation bytes: 90K (maximum 85,000 bytes)."

Then one level up from that restriction would be the totally alloc-free approach you mention which could potentially mean the GC could be put into a special idle/framework-only mode. For alloc-free, I believe you could enforce this at compile time, as opposed to run-time for the LOH condition.

[ Parent | on HN ]

Re:Microsoft: Rust Is the Industry’s ‘Best Chance’ at Safe S... by DaiPlusPlus on Saturday June 13, 2020 @03:59PM (#23512211)

Alloc-free would be nice if the CLR/CLI supported it, but I understand there’s too many major architectural changes required, e.g. to allow class object instances to live in the stack and limit their lifetime to prevent an invalid object reference. Even today you can’t `stackalloc` an array unless you’re using `unsafe`.

[ Parent | on HN ]