Cart
[Home] [By Thread] [By Date] [Recent Entries]
On 11/14/13 5:58 AM, Michael Kay wrote:
What we are saying in the latest draft is that f:convert(@code) is streamable provided the function signature of f:convert() declares its argument with an atomic type. If it doesn't declare the type, streaming fails. This interacts with the rules for packages, which say that when you override a function in another package, the signature must be compatible.Are you providing a pragma or something of the sort so programmers can declare their functions streamable, and raise a runtime error if it turns out not to be the case? Or is streamability entirely determined at compile-time? -Mike
|
