If you believe that "don't roll your own crypto" is some kind of absurd mantra the security industry uses to keep us in business, I recommend that you roll your own crypto, and keep us in business.
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?
Uhhh, except that this in no way actually implements CSP, given that more than one actor can just hang onto a resource despite having passed a pointer to someone else?
Who's meant to deal with freeing? Do you necessitate GC?
It's also fairly distasteful that all type safety is discarded.
I was very sad to discover that most of the hits (I only checked one page) for slash on stackoverflow are actually questions involving the slash character (Generally http request parsing)
For l1b there's no actual visa requirement, but the burden of proof for eligibility is still set incredibly high.
I understand to some degree the rationale behind the absurd process, at the same time it's incredibly frustrating to have a company that wants me here, and no avenue or realistic end in sight to make it happen.
Or because it's too expensive. Or it's getting in the way of more important things. Or too stressful. Or someone at the uni is making their life miserable. Or one of the other 10 million reasons that people drop out.
To presume that this decision is entirely motivated by how hard uni is is astonishingly naive, imo.
I dropped out super early. Worked for some software companies, built some internets.
Trying to get a US visa now, the decision to not get a degree is pretty bitter. That said, this is the first and I optimistically anticipate the last time a degree would have been any use to me, so I'll just power through and hope for the best.