>> (2) The language and implementation are still changing in breaking ways. > > Yep, I concede to this. My only question in response is whether it's valuable > to observe those changes in a project like this or even to use a project like > this to investigate other points of discussion, like: > > - Is there one Swift coding style? If not, what's ours? > - What do we need to implement in spite of, or for lack of, a standard > library feature? > > Or, just save all that for a rainy day, I suppose.
Interesting. I think it might be valuable to do these things in a limited project, if we can minimize the downside of breaking changes. Geoff _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
