[swift-evolution] Swift-based Metal Shading Language

Goffredo Marocchi panajev at gmail.com
Sun Jul 10 02:12:33 CDT 2016

I disagree. While it sounds nice to have a unified syntax working on C++ compatibility/interaction is  still quite key because of the mountains of legacy and new code still written everyday in it. Also, I think that the right language for the right domain and being able to glue them together is quite key in the modern computing world and using a single language in every computing domain is a chimera that can bring more pain than good.

Still, if we work out how to import C++ code well, you are probably going to get something very close to that you are wishing anyways :).

Sent from my iPhone

On 10 Jul 2016, at 07:17, Georgios Moschovitis via swift-evolution <swift-evolution at swift.org> wrote:

>> I *think* it'd be better to add C++ interoperability to Swift.
> Wouldn’t it be better to have unified syntax across the board? e.g.,
> int x; -vs- x: Int, etc?
> Using the same language/syntax would eliminate the taxing mental context-switch.
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution

More information about the swift-evolution mailing list