Just throwing this here. Unfortunately `Stream` is already taken (and tied to
Foundation).
public struct StdStream {
public struct StderrStream: OutputStream {
public func write(_ string: String) { fputs(string, Darwin.stderr) }
}
public struct StdoutStream: OutputStream {
public func write(_ string: String) { fputs(string, Darwin.stdout) }
}
public static var err = StderrStream()
public static var out = StdoutStream()
}
So in use, it would look something like
str.write(to: &StdStream.out)
str.write(to: &StdStream.err)
I also considered DarwinStream (seemed too on the nose), UnixStream, Streamfd,
BSDStream, etc. Didn't like any of them.
-- E, have paintbrush will bikeshed
> On Jul 11, 2016, at 12:58 PM, Saagar Jha via swift-evolution
> <[email protected]> wrote:
>
> Thanks, I’ll write it up.
>> On Jul 11, 2016, at 11:20, Dave Abrahams via swift-evolution
>> <[email protected]> wrote:
>>
>>
>> on Sun Jul 10 2016, Saagar Jha <[email protected]> wrote:
>>
>>> What is the process for smaller issues like these? I’m guessing that
>>> this doesn’t need a proposal; where should it go? On bugs.swift.org
>>> <http://bugs.swift.org/>?
>>
>> If it adds an API, it needs a proposal. Doesn't necessarily have to be
>> a big proposal, and the review period can be short, but we don't add
>> APIs without the evolution process.
>>
>> Thanks,
>> Dave
>>
>> --
>> Dave
>>
>> _______________________________________________
>> swift-evolution mailing list
>> [email protected]
>> https://lists.swift.org/mailman/listinfo/swift-evolution
>
> _______________________________________________
> swift-evolution mailing list
> [email protected]
> https://lists.swift.org/mailman/listinfo/swift-evolution
_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution
