<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Chris, thanks a lot for the answer, that's exactly what I wanted to read and it gives me hope for the language's future :)<div class=""><br class=""></div><div class="">- Elviro</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">Il giorno 12 dic 2016, alle ore 06:46, Chris Lattner <<a href="mailto:clattner@apple.com" class="">clattner@apple.com</a>> ha scritto:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">On Dec 11, 2016, at 5:48 AM, Elviro Rocca via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<div class=""><blockquote type="cite" class=""><div class=""><meta http-equiv="Content-Type" content="text/html charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Hi everyone, I read every post in the Higher-Kinded Types ( <a href="https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20151214/002736.html" class="">https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20151214/002736.html</a> ) thread from about a year ago, and I was wondering what's the status on the matter: I'm aware of the proposal draft ( <a href="https://github.com/typelift/swift/issues/1" class="">https://github.com/typelift/swift/issues/1</a> ), but I'd like to know if the Swift team has reconsidered the possible relevance of HKT for Swift in the foreseeable future.</div></div></div></blockquote><div class=""><br class=""></div>Hi Elviro,</div><div class=""><br class=""></div><div class="">HKT’s come up from time to time, so there is definitely interest, that said, I can’t imagine that this will be a priority to get done in Swift 4.</div><div class=""><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">By reading the discussion I found that the main concern from the Swift team was about practical use cases that could be of interest for a huge chunk of Swift developers: I don't think that a language feature should be there only if affects the majority of users, because of course you always have users at many different levels of awareness and understanding, not to mention experience and background, </div></div></div></blockquote><div class=""><br class=""></div><div class="">Right. I’m personally not opposed to having advanced features in Swift when they are highly motivated. We only aim to make sure that they only affect/benefit people who want to use them. Advanced features that beginners are forced to reckon with violate our goals to have a shallow learning curve. HKTs seem like they’d be fine in this regard.</div><div class=""><br class=""></div><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">but I understand that, considering the time constraints in language development and proposals review, the focus should (initially) be on things that matter the most to the vast majority of developers.</div></div></div></blockquote><br class=""></div><div class="">Right, this is the principle reason I can’t imagine that HKTs will get prioritized. There are a *TON* of improvements that will have widespread positive impact, and the Swift compiler team is very thinly spread. We are forced to pick and choose a few things that we think will have the biggest impact on the entire Swift community.</div><div class=""><br class=""></div><div class="">-Chris</div><br class=""></div></div></blockquote></div><br class=""></div></body></html>