Not that I need to say this, but I’ll chime in anyway with a big +1 to what
Chris said. =)
Fortunately, the current code owners for swift-corelibs-foundation are the same
people that work on Foundation for all of our other platforms. That means we’re
in a great position to make Foundation
Speaking of release cadence, do you think that Swift could transition to
the release train model (i.e., staged release, beta, and nightly) once
source and ABI compatibility are both established? That would allow a
quicker cadence and more testing of new library and language features. It's
seems to
On Jan 1, 2016, at 12:56 PM, Trent Nadeau wrote:
> Speaking of release cadence, do you think that Swift could transition to the
> release train model (i.e., staged release, beta, and nightly) once source and
> ABI compatibility are both established? That would allow a
Brilliant. Makes sense and seems to be a best-of-both-worlds approach.
- Rod
On 2 Jan 2016, at 3:16 PM, Chris Lattner wrote:
>>> On Jan 1, 2016, at 3:32 PM, Rod Brown wrote:
>>> Thanks Chris. I want to figure out what the guiding principles are
Please see response inline
- Rod
> On 2 Jan 2016, at 9:13 AM, Erica Sadun via swift-evolution
> wrote:
>
> Thanks Chris. I want to figure out what the guiding principles are before I
> blow any further proposal-capital. This gives me a good place to start
>
Thanks Chris. I want to figure out what the guiding principles are before I
blow any further proposal-capital. This gives me a good place to start chewing
on some thoughts. In particular, I'm considering two scenarios.
First, are things that seem unnaturally split between both places, such as
My understanding is that Foundation closely maps to the ObjC Foundation
framework.
Félix
> Le 31 déc. 2015 à 17:54:39, Erica Sadun via swift-evolution
> a écrit :
>
> Under what criteria should we propose moving items into the standard library
> and out from the
On Dec 31, 2015, at 2:54 PM, Erica Sadun via swift-evolution
wrote:
> Under what criteria should we propose moving items into the standard library
> and out from the standard library into Swift Foundation? Or will these things
> eventually merge and become one grand
On Jan 1, 2016, at 2:13 PM, Erica Sadun wrote:
> Thanks Chris. I want to figure out what the guiding principles are before I
> blow any further proposal-capital. This gives me a good place to start
> chewing on some thoughts. In particular, I'm considering two scenarios.
> On Jan 1, 2016, at 3:32 PM, Rod Brown wrote:
>> Thanks Chris. I want to figure out what the guiding principles are before I
>> blow any further proposal-capital. This gives me a good place to start
>> chewing on some thoughts. In particular, I'm considering two
Under what criteria should we propose moving items into the standard library
and out from the standard library into Swift Foundation? Or will these things
eventually merge and become one grand unified module sometime in the distant
future?
Thanks, -- E
11 matches
Mail list logo