Explore >> Select a destination
|
You are here 
|
ashishkakkad.com | ||
| | | | |
peanball.net
|
|
| | | | | ||
| | | | |
www.cs.cornell.edu
|
|
| | | | | I did some iOS programming recently (for an unknown reason). Using the new Swift language has made it evident the language is young-and, like a rebellious teenager, it conflicts with its much older framework counterpart, Cocoa. Here are two places where the disconnect is most stark, and where Swift should grow more sophisticated type-system features. | |
| | | | |
iosdeveloperzone.com
|
|
| | | | | I am guessing early on in the development of the Swift language the relationship between a function declaration's parameter labels and whether they need to be included in a call was much more forward. Maybe it looked something like this. But then they decided that to make Swift play nice with Cocoa that labels would | |
| | | | |
www.cppstories.com
|
|
| | | For C++17 everyone wanted to have concepts, and as you know, we didn't get them. But does it mean C++17 doesn't improve templates/template meta-programming? Far from that! In my opinion, we get excellent features. Read more for details. Intro Do you work a lot with templates and meta-programming? With C++17 we get a few nice improvements: some are quite small, but also there are notable features as well! | ||
