Re: [swift-evolution] pitch: Unified libc import (again)

2017-08-21 Thread Philippe Hausler via swift-evolution
> On Aug 18, 2017, at 5:42 PM, Xiaodi Wu via swift-evolution > wrote: > > On Fri, Aug 18, 2017 at 7:39 PM, Taylor Swift > wrote: > > > On Fri, Aug 18, 2017 at 8:09 PM, Xiaodi Wu

Re: [swift-evolution] pitch: Unified libc import (again)

2017-08-18 Thread Xiaodi Wu via swift-evolution
On Fri, Aug 18, 2017 at 7:39 PM, Taylor Swift wrote: > > > On Fri, Aug 18, 2017 at 8:09 PM, Xiaodi Wu wrote: > >> On Fri, Aug 18, 2017 at 6:55 PM, Greg Parker wrote: >> >>> >>> On Aug 17, 2017, at 5:16 PM, Xiaodi Wu via

Re: [swift-evolution] pitch: Unified libc import (again)

2017-08-18 Thread Taylor Swift via swift-evolution
On Fri, Aug 18, 2017 at 8:09 PM, Xiaodi Wu wrote: > On Fri, Aug 18, 2017 at 6:55 PM, Greg Parker wrote: > >> >> On Aug 17, 2017, at 5:16 PM, Xiaodi Wu via swift-evolution < >> swift-evolution@swift.org> wrote: >> >> On Thu, Aug 17, 2017 at 6:46 PM, Taylor

Re: [swift-evolution] pitch: Unified libc import (again)

2017-08-18 Thread Xiaodi Wu via swift-evolution
On Fri, Aug 18, 2017 at 6:55 PM, Greg Parker wrote: > > On Aug 17, 2017, at 5:16 PM, Xiaodi Wu via swift-evolution < > swift-evolution@swift.org> wrote: > > On Thu, Aug 17, 2017 at 6:46 PM, Taylor Swift > wrote: > >> I don’t think the “is this library

Re: [swift-evolution] pitch: Unified libc import (again)

2017-08-18 Thread Saagar Jha via swift-evolution
Just thought I’d link the previous thread on this topic: https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20160704/023927.html . I had promised to write a proposal for it back then, but never got

Re: [swift-evolution] pitch: Unified libc import (again)

2017-08-18 Thread Greg Parker via swift-evolution
> On Aug 17, 2017, at 5:16 PM, Xiaodi Wu via swift-evolution > wrote: > > On Thu, Aug 17, 2017 at 6:46 PM, Taylor Swift > wrote: > I don’t think the “is this library functionality or standard library >

Re: [swift-evolution] pitch: Unified libc import (again)

2017-08-18 Thread Daniel Dunbar via swift-evolution
> On Aug 17, 2017, at 3:47 PM, Taylor Swift wrote: > > > > On Thu, Aug 17, 2017 at 3:50 PM, Daniel Dunbar > wrote: > > > On Aug 17, 2017, at 9:26 AM, Taylor Swift via swift-evolution > >

Re: [swift-evolution] pitch: Unified libc import (again)

2017-08-18 Thread Xiaodi Wu via swift-evolution
Not “fundamentally” incompatible: var stderr = FileHandle.standardError /* Conform FileHandle to TextOutputStream */ print("foo", to: ) On Fri, Aug 18, 2017 at 01:39 Brent Royal-Gordon wrote: > On Aug 17, 2017, at 8:20 PM, Xiaodi Wu via swift-evolution < >

Re: [swift-evolution] pitch: Unified libc import (again)

2017-08-17 Thread Taylor Swift via swift-evolution
On Thu, Aug 17, 2017 at 11:19 PM, Xiaodi Wu wrote: > On Thu, Aug 17, 2017 at 22:06 Taylor Swift wrote: > >> Okay I can sense this thread getting derailed so I’ll try to address your >> comments one by one. >> >> * stderr should go wherever stdin and

Re: [swift-evolution] pitch: Unified libc import (again)

2017-08-17 Thread Taylor Swift via swift-evolution
Okay I can sense this thread getting derailed so I’ll try to address your comments one by one. * stderr should go wherever stdin and stdout go. Since it’d be silly for a function like `print(_:separator:terminator:)` or ` readLine(strippingNewline:)` to live anywhere but the standard library,

Re: [swift-evolution] pitch: Unified libc import (again)

2017-08-17 Thread Xiaodi Wu via swift-evolution
On Thu, Aug 17, 2017 at 6:46 PM, Taylor Swift wrote: > I don’t think the “is this library functionality or standard library > functionality” argument is worth having, but if stdout and stdin are > first-class citizens in the Swift world, so should stderr. > > As for

Re: [swift-evolution] pitch: Unified libc import (again)

2017-08-17 Thread Taylor Swift via swift-evolution
I don’t think the “is this library functionality or standard library functionality” argument is worth having, but if stdout and stdin are first-class citizens in the Swift world, so should stderr. As for bringing Foundation into the discussion, you can’t really talk about Foundation without also

Re: [swift-evolution] pitch: Unified libc import (again)

2017-08-17 Thread Xiaodi Wu via swift-evolution
IMO, you’re touching on at least three or four separate topics here. Daniel touched on several, but just some comments/questions: * Standard error output is something that’s been discussed here previously. I believe the last pitch had something like StandardError being added to the standard

Re: [swift-evolution] pitch: Unified libc import (again)

2017-08-17 Thread Taylor Swift via swift-evolution
Python’s os.path is a nice abstract model for doing path manipulations. Maybe Swift could get a struct like `Filepath` or something on which these operations could be done. On Thu, Aug 17, 2017 at 6:47 PM, Taylor Swift wrote:

Re: [swift-evolution] pitch: Unified libc import (again)

2017-08-17 Thread Taylor Swift via swift-evolution
On Thu, Aug 17, 2017 at 3:50 PM, Daniel Dunbar wrote: > > > On Aug 17, 2017, at 9:26 AM, Taylor Swift via swift-evolution < > swift-evolution@swift.org> wrote: > > > > I know this has come up before without any action, but having the > standard C library be packaged

[swift-evolution] pitch: Unified libc import (again)

2017-08-17 Thread Taylor Swift via swift-evolution
I know this has come up before without any action, but having the standard C library be packaged under `Darwin` on OSX and `Glibc` under Linux is something that’s really becoming an issue as the Swift package ecosystem matures. Right now a lot of packages are a lot less portable than they could be