> On Jan 1, 2018, at 10:47 PM, Chris Lattner via swift-evolution
> wrote:
>
>> On Dec 31, 2017, at 12:14 PM, Matthew Johnson via swift-evolution
>> > wrote:
>>
>> I agree that we need a solution to the
> On Dec 31, 2017, at 12:14 PM, Matthew Johnson via swift-evolution
> wrote:
>
> I agree that we need a solution to the problem described. I also agree that
> non-exhaustive is most in keeping with the overall design of Swift at module
> boundaries. However, I
This would be a good addition to the BinaryFloatingPoint protocol. It's not
difficult to implement; it's not present (afaict) simply because
BinaryFloatingPoint was designed before BinaryInteger existed.
On Mon, Jan 1, 2018 at 3:58 PM, Kelvin Ma via swift-evolution <
swift-evolution@swift.org>
title says it all,, this is kind of annoying when writing some generic
FloatingPoint code where both the integral and floating parameters are
unfixed.
___
swift-evolution mailing list
swift-evolution@swift.org
Happy new year from klossyland!
On Mon, Jan 1, 2018 at 11:23 AM, Georgios Moschovitis via swift-users <
swift-us...@swift.org> wrote:
> Happy new year! Greetings from Cyprus :)
>
> George.
>
> On 1 Jan 2018, at 1:42 AM, Adrian Zubarev via swift-users <
> swift-us...@swift.org> wrote:
>
> Well
Happy new year! Greetings from Cyprus :)
George.
> On 1 Jan 2018, at 1:42 AM, Adrian Zubarev via swift-users
> wrote:
>
> Well some of you guys have to wait a little longer, but I can already wish
> everyone a happy new year from Germany.
>
> --
> Adrian
Happy New Year!
> On Dec 31, 2017, at 6:01 PM, Goffredo Marocchi via swift-evolution
> wrote:
>
> Happy new year everybody :)!
>
> Sent from my iPhone
>
> On 31 Dec 2017, at 23:43, David Hart via swift-evolution
>