Re: FFI, safe vs unsafe

Taral writes:

fast - takes very little time to execute

I was thinking about "quick". It seems to be less literal about speed if my feeling of English is good enough; the effect is indeed not just speed. They fit both as a description of the foreign function, and as a request from an implementation (to make the call faster at the expense of something). The trouble with both is that they raise the question "shouldn't I mark all FFI calls as fast, so they are faster?". They don't hint at a cost of the optimization: faster at the expense of what? -- __("< Marcin Kowalczyk \__/ qrczak@knm.org.pl ^^ http://qrnik.knm.org.pl/~qrczak/