Xcode 10.1 swift 4.2 operator overloading causing compiler warning: “All paths through this function will...
So I suddenly have this compiler warning that was not present on swift 3 or (I think) swift 4.0.
the code below overloads the += operator to perform a vector increment:
public func += ( left: inout CGVector, right: CGVector) {
left += right
}
and produces the warning, I am puzzled can anyone shed light on why the warning is thrown and what is wrong?
swift swift4.2
add a comment |
So I suddenly have this compiler warning that was not present on swift 3 or (I think) swift 4.0.
the code below overloads the += operator to perform a vector increment:
public func += ( left: inout CGVector, right: CGVector) {
left += right
}
and produces the warning, I am puzzled can anyone shed light on why the warning is thrown and what is wrong?
swift swift4.2
I don't know swift, but here you seem to overload +=, and then immediately call it. So your stacktrace should look like this: += (a, b) -> += (a,b) -> += (a,b) ...
– dyukha
Nov 24 '18 at 5:54
You are simply calling overloaded function "+=" within itself. I guess replacingleft += right
withleft = left + right
will solve the problem.
– Rakesh Pethani
Nov 24 '18 at 6:40
add a comment |
So I suddenly have this compiler warning that was not present on swift 3 or (I think) swift 4.0.
the code below overloads the += operator to perform a vector increment:
public func += ( left: inout CGVector, right: CGVector) {
left += right
}
and produces the warning, I am puzzled can anyone shed light on why the warning is thrown and what is wrong?
swift swift4.2
So I suddenly have this compiler warning that was not present on swift 3 or (I think) swift 4.0.
the code below overloads the += operator to perform a vector increment:
public func += ( left: inout CGVector, right: CGVector) {
left += right
}
and produces the warning, I am puzzled can anyone shed light on why the warning is thrown and what is wrong?
swift swift4.2
swift swift4.2
edited Nov 24 '18 at 13:20
wvteijlingen
8,57112544
8,57112544
asked Nov 24 '18 at 5:51
Stephen SpringettStephen Springett
183
183
I don't know swift, but here you seem to overload +=, and then immediately call it. So your stacktrace should look like this: += (a, b) -> += (a,b) -> += (a,b) ...
– dyukha
Nov 24 '18 at 5:54
You are simply calling overloaded function "+=" within itself. I guess replacingleft += right
withleft = left + right
will solve the problem.
– Rakesh Pethani
Nov 24 '18 at 6:40
add a comment |
I don't know swift, but here you seem to overload +=, and then immediately call it. So your stacktrace should look like this: += (a, b) -> += (a,b) -> += (a,b) ...
– dyukha
Nov 24 '18 at 5:54
You are simply calling overloaded function "+=" within itself. I guess replacingleft += right
withleft = left + right
will solve the problem.
– Rakesh Pethani
Nov 24 '18 at 6:40
I don't know swift, but here you seem to overload +=, and then immediately call it. So your stacktrace should look like this: += (a, b) -> += (a,b) -> += (a,b) ...
– dyukha
Nov 24 '18 at 5:54
I don't know swift, but here you seem to overload +=, and then immediately call it. So your stacktrace should look like this: += (a, b) -> += (a,b) -> += (a,b) ...
– dyukha
Nov 24 '18 at 5:54
You are simply calling overloaded function "+=" within itself. I guess replacing
left += right
with left = left + right
will solve the problem.– Rakesh Pethani
Nov 24 '18 at 6:40
You are simply calling overloaded function "+=" within itself. I guess replacing
left += right
with left = left + right
will solve the problem.– Rakesh Pethani
Nov 24 '18 at 6:40
add a comment |
1 Answer
1
active
oldest
votes
When you do left += right
, it calls the same function that you were defining. In other words, your operator overload function += ( left: inout CGVector, right: CGVector)
will call itself in all times (infinite recursion). You are doing something like
func foo(String: bar) {
foo(bar)
}
But just by replacing foo
with +=
, which is not logical. Xcode only gives you a warning now though, it is not an error that stops you from compiling. You probably have written this function wrong in the past (but the warning reminding you this was just added to the compiler).
You probably want something like this
public func += ( left: inout CGVector, right: CGVector) {
left = CGVector(dx: left.dx + right.dx, dy: left.dy + right.dy)
}
Sometimes even when the answer is staring you in the face you just can’t see it. Thanks now I see the obvious.
– Stephen Springett
Nov 24 '18 at 6:43
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53455545%2fxcode-10-1-swift-4-2-operator-overloading-causing-compiler-warning-all-paths-t%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
When you do left += right
, it calls the same function that you were defining. In other words, your operator overload function += ( left: inout CGVector, right: CGVector)
will call itself in all times (infinite recursion). You are doing something like
func foo(String: bar) {
foo(bar)
}
But just by replacing foo
with +=
, which is not logical. Xcode only gives you a warning now though, it is not an error that stops you from compiling. You probably have written this function wrong in the past (but the warning reminding you this was just added to the compiler).
You probably want something like this
public func += ( left: inout CGVector, right: CGVector) {
left = CGVector(dx: left.dx + right.dx, dy: left.dy + right.dy)
}
Sometimes even when the answer is staring you in the face you just can’t see it. Thanks now I see the obvious.
– Stephen Springett
Nov 24 '18 at 6:43
add a comment |
When you do left += right
, it calls the same function that you were defining. In other words, your operator overload function += ( left: inout CGVector, right: CGVector)
will call itself in all times (infinite recursion). You are doing something like
func foo(String: bar) {
foo(bar)
}
But just by replacing foo
with +=
, which is not logical. Xcode only gives you a warning now though, it is not an error that stops you from compiling. You probably have written this function wrong in the past (but the warning reminding you this was just added to the compiler).
You probably want something like this
public func += ( left: inout CGVector, right: CGVector) {
left = CGVector(dx: left.dx + right.dx, dy: left.dy + right.dy)
}
Sometimes even when the answer is staring you in the face you just can’t see it. Thanks now I see the obvious.
– Stephen Springett
Nov 24 '18 at 6:43
add a comment |
When you do left += right
, it calls the same function that you were defining. In other words, your operator overload function += ( left: inout CGVector, right: CGVector)
will call itself in all times (infinite recursion). You are doing something like
func foo(String: bar) {
foo(bar)
}
But just by replacing foo
with +=
, which is not logical. Xcode only gives you a warning now though, it is not an error that stops you from compiling. You probably have written this function wrong in the past (but the warning reminding you this was just added to the compiler).
You probably want something like this
public func += ( left: inout CGVector, right: CGVector) {
left = CGVector(dx: left.dx + right.dx, dy: left.dy + right.dy)
}
When you do left += right
, it calls the same function that you were defining. In other words, your operator overload function += ( left: inout CGVector, right: CGVector)
will call itself in all times (infinite recursion). You are doing something like
func foo(String: bar) {
foo(bar)
}
But just by replacing foo
with +=
, which is not logical. Xcode only gives you a warning now though, it is not an error that stops you from compiling. You probably have written this function wrong in the past (but the warning reminding you this was just added to the compiler).
You probably want something like this
public func += ( left: inout CGVector, right: CGVector) {
left = CGVector(dx: left.dx + right.dx, dy: left.dy + right.dy)
}
answered Nov 24 '18 at 6:24
paper1111paper1111
3,19411833
3,19411833
Sometimes even when the answer is staring you in the face you just can’t see it. Thanks now I see the obvious.
– Stephen Springett
Nov 24 '18 at 6:43
add a comment |
Sometimes even when the answer is staring you in the face you just can’t see it. Thanks now I see the obvious.
– Stephen Springett
Nov 24 '18 at 6:43
Sometimes even when the answer is staring you in the face you just can’t see it. Thanks now I see the obvious.
– Stephen Springett
Nov 24 '18 at 6:43
Sometimes even when the answer is staring you in the face you just can’t see it. Thanks now I see the obvious.
– Stephen Springett
Nov 24 '18 at 6:43
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53455545%2fxcode-10-1-swift-4-2-operator-overloading-causing-compiler-warning-all-paths-t%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I don't know swift, but here you seem to overload +=, and then immediately call it. So your stacktrace should look like this: += (a, b) -> += (a,b) -> += (a,b) ...
– dyukha
Nov 24 '18 at 5:54
You are simply calling overloaded function "+=" within itself. I guess replacing
left += right
withleft = left + right
will solve the problem.– Rakesh Pethani
Nov 24 '18 at 6:40