richo
Joined 15 years ago
Joined 15 years ago
This is cute.
My question about deallocation was regarding the resource though, not the channel.
Honestly, while from a best practice sense it shouldn't be too hard (You need to either send or free a resource when you're done with it), in practice my intuition is that codebases using this will be rife with exciting use after free bugs.
Seperately, have you done any testing to see what valgrind makes of it?
Who's meant to deal with freeing? Do you necessitate GC?
It's also fairly distasteful that all type safety is discarded.
C doesn't define behaviour of a null deref, but most compilers map a -rwx page there to ensure that attempts to deref fault.
In what circumstance do they not?
Watch the "3d layout engine" flip out thoroughly (tested only on chrome stable on darwin)
We basically have a gimme with the E3, but it has the degree requirement.
[ my public key: https://keybase.io/richo; my proof: https://keybase.io/richo/sigs/6BEdMPB9A3K5j8kz-G7J_nFkbHpHzr1cCswu9oV3M4Y ]