> If you feel the need for it, feel free to use some interface macro. And not > again this "it needs to be in the stdlib!". Point (2) applies for "must be in > stdlib" too.
Well, I'm the one who suggested than an interface macro should be in the stdlib and I feel somehow bad for it. In fact what I'd like to see in the stdlib is standard types (but not necessarily implementations) where every implementation could agree on. In particular for I/O streams. I believe we need good streams types that could be implemented by a HTTP server library, by the operating system files or anything in between that could suit the need for everyone. std/streams, last time I checked, is not very good at that. The reason why I said that iface should be in stdlib is because this is a way I know where multiple parties can agree on an interface not tied to a specific implementation. But anything that could do the job of standard types would equally work well in my opinion.
