>>
>> Here’s a simple, yet tragic example: BOOL in Objective-C. We were
>> stuck with signed char instead of getting a real boolean. Back in 10.4
>> Tiger when the Intel migration was announced, I filed a bug report
>> reminding them that this was the chance to fix this. They didn’t fix
>> it, so w
So I don’t mind (too much) if it takes longer to get a stable ABI. It
makes my life harder, but on the flip-side, I don’t want to be stuck
with yet another broken language and ABI. I want this done right
because it will be almost impossible to fix later.
Here’s a simple, yet tragic example: BOOL i
On 5/16/16, Chris Lattner wrote:
> On May 16, 2016, at 2:27 PM, Eric Wing via swift-evolution
> wrote:
>>> I'm not an expert in the Linux communities needs and desires. That
>>> said,
>>> from what I understand, they don’t care at all about ABI stability,
> I'm not an expert in the Linux communities needs and desires. That said,
> from what I understand, they don’t care at all about ABI stability, since
> everything is typically built from source.
>
> -Chris
>
>
Not exactly true. (I care.)
Video games (e.g. Steam/Linux) care deeply about ABI stab
