Hi all, and particularly Saleem, Hugh, and Han,
I've been recently trying to build the Swift compiler, runtime, and core
libraries on Windows against the MSVC runtime from master and have been running
into some difficulties. I've managed to get Clang and swiftc built (and I hope
to submit pull
Hi Jordan and David,
Reading this from a user’s perspective, I’d be very much in favour of something
like the @abi annotation. The core issue I see with the ‘allow renaming’
approach is that users coming to Swift from other languages will do so with the
expectation that ordering is significant
A -1 from me to deprecating the mode. I’ve been using Swift in high-performance
situations such as in a game engine, where in particular thing like integer
overflow checks become a measurable cost in tight inner loops. Currently I
can’t use Array in many places due to ownership issues and retain
I've been working on getting Swift running properly on 64-bit Windows and
wanted to get some feedback/ideas on a specific issue.
In swift/Runtime/HeapObject.h, there is a TwoWordPair::Return type intended to
return two word-sized values in registers. On Windows, structs are returned
indirectl
Hi all,
I've had a PR (https://github.com/apple/swift/pull/13140) that's been open for
about 10 days with a few CMake changes to fix the Windows cross-compile build.
I wasn't sure who best to ask to review it, but was suggested to post here with
it.
Could someone familiar with that area maybe
