[swift-evolution] Dynamic Class/Struct Definition At Run Time

Ted F.A. van Gaalen tedvgiosdev at gmail.com
Wed Oct 12 15:37:47 CDT 2016

Hi David,

Thanks for your reply., OK, I think I understand. 

It then is a capacity problem, right?

In effect, it means restricting people from bringing perhaps very valuable 
(not necessarily my contributions) 
and essential ideas forward, which could play a crucial role improving Swift.

I think this is a very negative aspect. surely bouncing creative people away,
dropping their efforts and interest here altogether. 

The question then remains, where / when / how can one bring topics 
that are taking a longer stretch and are not bound to a certain release of Swift,
seemingly “outside” of this restriction under attention?

if swift evolution is (currently? ) not open for new ideas/topics:
I thought that was the primary purpose of Swift evolution?

Kind Regards

> On 12 Oct 2016, at 21:48, David Hart <david at hartbit.com> wrote:
> Hello Ted,
> Please try to understand. As Xiaodi and others have said a few times, it has nothing to do with the topic being important or interesting. The current phase of Swift 4’s development does not allow any extensive discussion or review on topics which do not impact ABI stability:
> Stage 1 focuses on the essentials required for source and ABI stability. Features that don't fundamentally change the ABI of existing language features or imply an ABI-breaking change to the standard library will not be considered in this stage.
>> On 12 Oct 2016, at 19:14, Ted F.A. van Gaalen via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
>> Apart from my perhaps fierce reaction, I am not aware of doing something wrong.
>> and I still find this topic very important. 
> David.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20161012/7e4f7797/attachment.html>

More information about the swift-evolution mailing list