Oh gosh yes. I’ve been working on a bug off and on for a while, and half the reason it isn’t fixed yet is that I can’t wrap my head around how modern compilers work (which isn’t really saying much since this is the only compiler I’ve looked at).
> On Jul 29, 2016, at 11:32 AM, Brandon Knope via swift-evolution > <[email protected]> wrote: > > This too. I think some better documentation for all of us could pay great > dividends. Or a primer of some sort. A weekly series diving into the common > parts of LLVM? > > Brandon > >> On Jul 29, 2016, at 12:30 PM, Karl <[email protected] >> <mailto:[email protected]>> wrote: >> >> >>> On 29 Jul 2016, at 18:01, Brandon Knope via swift-evolution >>> <[email protected] <mailto:[email protected]>> wrote: >>> >>> I think this just shows how familiar many of us are with this process. >>> >>> It’s fun and challenging coming up with the great ideas…but someone has to >>> implement it. It may not be fun…and it may be very time consuming. >>> >>> I think a lot of us just expected the core team to implement these all…but >>> they really need help from the community to save them time and sanity with >>> trying to get all of this done. >>> >>> >>> To me this means I need to familiarize myself with the swift code base even >>> more. I need to understand all the GitHub processes to get a change >>> implemented and submitted. >>> >>> I really hope at some point someone can make a primer of the process they >>> went through to implement one of these proposals from start to finish. I >>> think this could be illuminating for many on this list. >>> >>> ALSO: I think this is where a forum can help greatly: some of us need a way >>> to discuss our implementations and ask for help while we are working on one >>> of these proposals. Mailing lists make it very hard to have a general >>> discussion where we talk code and ask for help in get detail. It is also >>> much easier for others to browse to learn from that conversation. >>> >>> In short: the swift-evolution process works…but some of us in the community >>> need to step up and help a little more other than just proposing things. I >>> think the swift team could make this easier with some detailed guides and >>> documentation and a forum for better discussions when trying to implement >>> these things…but I know they are insanely busy. I do think some time >>> investment in this area will pay off in the future…and quickly. >>> >>> Brandon >>> >>>> On Jul 29, 2016, at 11:15 AM, Félix Cloutier via swift-evolution >>>> <[email protected] <mailto:[email protected]>> wrote: >>>> >>>> Hello all, >>>> >>>> With the Swift 3 deadline passed, according to the Swift Evolution >>>> progress page, about 20% of the proposals that the community voted in >>>> won't make it for Swift 3. Beyond the implications for the language >>>> itself, what does that mean for the swift-evolution process? >>>> >>>> Félix >>>> >>>> _______________________________________________ >>>> swift-evolution mailing list >>>> [email protected] <mailto:[email protected]> >>>> https://lists.swift.org/mailman/listinfo/swift-evolution >>>> <https://lists.swift.org/mailman/listinfo/swift-evolution> >>> >>> _______________________________________________ >>> swift-evolution mailing list >>> [email protected] <mailto:[email protected]> >>> https://lists.swift.org/mailman/listinfo/swift-evolution >>> <https://lists.swift.org/mailman/listinfo/swift-evolution> >> >> The thing that’s stopping me contributing to the compiler itself is that it >> uses LLVM types and functions, and I don’t know them. The Swift compiler >> itself looks very clean and approachable. >> >> And then, when you try to look up any of those LLVM functions, you get >> Doxygen, which isn’t really great. It just puts me off really getting to >> grips with LLVM’s conventions. Maybe one day when I have more time. >> >> Unless somebody knows of some better documentation? >> >> Karl > > _______________________________________________ > swift-evolution mailing list > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
