Dear Joe, Chris, Swift Community,
Here is my quick fire view.
What about adding a builtin directive called environ(...) for holding
OS-specific environmental differences. So in the case of Windows, we would
potentially have environ(msvc), environ(cygwin), environ(mingw),
environ(nano) etc. Thus,
Why is there a need to support Cygwin/MingW and their variants as a
build target for Windows? MSVC is practically free these days.
Doesn't supporting multiple different ABI targets on Windows just
complicate matters unnecessarily? Isn't MSVC enough as a build target?
I am not dejecting; rather, j
Chris,
The proposed syntax looks and reads so much better! +1.
On 15 April 2016 at 05:57, Chris Lattner via swift-evolution
wrote:
> We currently accept function type syntax without parentheses, like:
>
> Int -> Float
> String -> ()
>
> etc. The original rationale aligned with the fact that
Travis / Michael,
+1 on built-in support for Crypto libraries in swift-corelibs.
On 14 April 2016 at 22:52, Michael Ilseman via swift-evolution
wrote:
> Great! I will watch that thread as it’s something I’m also interested in
> knowing more about. Thanks for bringing it up!
>
> On Apr 14, 2016
How about "<-"?
I could see a few shorthands with that for Strings, etc. :-)
On 10 April 2016 at 22:03, Jean-Daniel Dupas via swift-evolution
wrote:
>
> Le 10 avr. 2016 à 15:01, Антон Жилин via swift-evolution
> a écrit :
>
> & (as a prefix operator), ->, ?, and ! (as a postfix operator)
>
> Th
Chris,
Thanks. The distraction factor makes sense. I will update SR-1134 as
discussed and mark it as post Swift v3.
On 9 April 2016 at 14:13, Chris Lattner wrote:
>
> On Apr 8, 2016, at 8:02 AM, hitstergtd+swiftevo--- via swift-evolution
> wrote:
>
> Chris,
>
> Thanks
hopefully the above would ensure that
it isn't forgotten. :)
> On 8 April 2016 at 07:01, Chris Lattner wrote:
>>
>>> On Apr 7, 2016, at 12:28 PM, hitstergtd+swiftevo--- via swift-evolution
>>> wrote:
>>>
>>> To the community:
>>>
&g
To the community:
Neither am I a compiler/language design expert nor have I previously
written a proposal to that effect, so I apologise if I have
trivialised the matter especially with regard to other parts of Swift
or if some of it already exists. I am also aware that what I've
proposed herein m