> On Nov 3, 2017, at 9:59 PM, Chris Lattner <clatt...@nondot.org> wrote: > > >> On Nov 3, 2017, at 8:40 AM, Dave DeLong via swift-evolution >> <swift-evolution@swift.org> wrote: >> >> That’s cool, but a hygienic macro system isn’t anywhere on the Swift roadmap. >> >> Chris has mentioned in interviews that such a system is "a big feature >> that’s open-ended and requires a huge design process” which makes >> off-the-table for Swift 5, and (I’m guessing) unlikely for Swift 6 too. >> >> Personally I’d like to be able to better debug my apps in Swift 4.1 rather >> than waiting another 2 or 3 years for a magical macro system to somehow >> solve this. > > You’re assuming somehow that this is an “easy” feature. I haven’t seen a > concrete proposal, but I don’t see how adding hidden options to operators > compose into the existing system. > > -Chris
It’s possible I missed something, but my attempt at implementing it only touched 3 files. One was the actual implementation, another was adapting the diagnostics messages, and the third was the tests. I’m still new to building swift myself, but the tests all passed... https://github.com/davedelong/swift/commit/c65c634a59b63add0dc9df1ac8803e9d70bfa697 As for a formal proposal, I’ll hopefully have some time this weekend to put that together. Can you expound some more on what you mean by hidden options to operators not composing into the existing system? I’m not sure I follow. Dave >
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
