> On Nov 10, 2017, at 3:05 PM, Joe Groff wrote:
>
>
>
>> On Nov 8, 2017, at 9:59 PM, Erik Eckstein via swift-dev
>> wrote:
>>
>>
>>
>>> On Nov 8, 2017, at 5:27 PM, Johannes Weiß via swift-dev
>>> wrote:
>>>
>>> Hi Daniel,
>>>
On 2 Nov 2017, at 8:15 pm, Daniel Dunbar wrote:
> On Nov 8, 2017, at 9:59 PM, Erik Eckstein via swift-dev
> wrote:
>
>
>
>> On Nov 8, 2017, at 5:27 PM, Johannes Weiß via swift-dev
>> wrote:
>>
>> Hi Daniel,
>>
>>> On 2 Nov 2017, at 8:15 pm, Daniel Dunbar wrote:
>>>
>>> My personal preference is to:
>>> 1. Do nothing for now, but enc
> On Nov 8, 2017, at 5:27 PM, Johannes Weiß wrote:
>
> Hi Daniel,
>
>> On 2 Nov 2017, at 8:15 pm, Daniel Dunbar wrote:
>>
>> My personal preference is to:
>> 1. Do nothing for now, but encourage publishing standardized protocols to
>> solve this need.
>> 2. Hope for a future with WMO+LTO mag
> On Nov 8, 2017, at 5:27 PM, Johannes Weiß via swift-dev
> wrote:
>
> Hi Daniel,
>
>> On 2 Nov 2017, at 8:15 pm, Daniel Dunbar wrote:
>>
>> My personal preference is to:
>> 1. Do nothing for now, but encourage publishing standardized protocols to
>> solve this need.
>> 2. Hope for a futur
Hi Daniel,
> On 2 Nov 2017, at 8:15 pm, Daniel Dunbar wrote:
>
> My personal preference is to:
> 1. Do nothing for now, but encourage publishing standardized protocols to
> solve this need.
> 2. Hope for a future with WMO+LTO magic which recovers the performance, for
> the case where the entir
My personal preference is to:
1. Do nothing for now, but encourage publishing standardized protocols to solve
this need.
2. Hope for a future with WMO+LTO magic which recovers the performance, for the
case where the entire application ends up using one implementation.
You can manage some of the
