4 ms·
From TFA: // Returns the smallest factor of `n` > 1, and // whether `n` itself is prime. fn SmallestFactor(n: i32) -> (i32, bool) { This is so unlike C+
by PaulDavisThe1st 4y ago
From TFA:
// Returns the smallest factor of `n` > 1, and
// whether `n` itself is prime.
fn SmallestFactor(n: i32) -> (i32, bool) {
This is so unlike C++ I cannot see how anyone can consider it a successor language. It might, in fact, be a much better language, but it is not a successor when you're going to change syntax this much, and in a way that will be hard to automate (precisely because of the "most vexing parse" problem(s).
- yoz-y 4y agoSwift is a successful successor to Objective-C and their syntaxes and idioms are worlds apart. It’s about what class of problems you can solve in the language.
- PaulDavisThe1st 4y agoI don't agree with your analysis. But that's fine.
- jack_h 4y agoIs that really so different from the following C++ equivalent? auto SmallestFactor(int32_t n) -> std::pair<int32_t, bool> { ... }
- PaulDavisThe1st 4y agoI guess I don't understand what role the -> plays there. I must be too old school, I suppose.
- alpaca128 4y agoI can't speak for the C++ example, but in your code snippet `->` points to the return type. The function takes an integer argument and effectively turns it into a tuple, so: `f(i32) -> (i32, bool)`.
- int_19h 4y agoIn this particular example, all it does is reverse the order of return type wrt arguments and function name. I still find this syntax more readable with complicated return types because you no longer have to carefully parse it to see where the type ends and the name begins. In the more general case, having the return type follow the function name means that it can reference parameters in sizeof(), decltype() etc.