Segmentation fault: 11 Xcode 10.1
My code worked fine on in Xcode 9.x.x. But not worked in Xcode 10. I am getting compile time error. My code like this:
protocol A {
}
protocol B {
associatedtype T: A
func b(p: T)
}
class L<P>: A {
}
class C<K, O: L<K>>: B {
func b(p: O) {
}
}
swift xcode generics
asked Nov 8 '18 at 5:05
Shohin
312
add a comment |
My code worked fine on in Xcode 9.x.x. But not worked in Xcode 10. I am getting compile time error. My code like this:
protocol A {
}
protocol B {
associatedtype T: A
func b(p: T)
}
class L<P>: A {
}
class C<K, O: L<K>>: B {
func b(p: O) {
}
}
swift xcode generics
asked Nov 8 '18 at 5:05
Shohin
312
4
Your title says you have a segmentation fault which is a runtime error but your question says you have a compile time error. Which is it? If you have a runtime error, show code that actually causes the error.
– rmaddy
Nov 8 '18 at 5:08
I checked, and the code Shohin provided does cause the Swift compiler to crash with a segmentation fault.
– Brent Royal-Gordon
Nov 13 '18 at 0:51
add a comment |
My code worked fine on in Xcode 9.x.x. But not worked in Xcode 10. I am getting compile time error. My code like this:
protocol A {
}
protocol B {
associatedtype T: A
func b(p: T)
}
class L<P>: A {
}
class C<K, O: L<K>>: B {
func b(p: O) {
}
}
swift xcode generics
asked Nov 8 '18 at 5:05
Shohin
312
My code worked fine on in Xcode 9.x.x. But not worked in Xcode 10. I am getting compile time error. My code like this:
protocol A {
}
protocol B {
associatedtype T: A
func b(p: T)
}
class L<P>: A {
}
class C<K, O: L<K>>: B {
func b(p: O) {
}
}
swift xcode generics
swift xcode generics
asked Nov 8 '18 at 5:05
Shohin
312
asked Nov 8 '18 at 5:05
Shohin
312
asked Nov 8 '18 at 5:05
Shohin
312
asked Nov 8 '18 at 5:05
Shohin
312
asked Nov 8 '18 at 5:05
Shohin
312
312
4
Your title says you have a segmentation fault which is a runtime error but your question says you have a compile time error. Which is it? If you have a runtime error, show code that actually causes the error.
– rmaddy
Nov 8 '18 at 5:08
I checked, and the code Shohin provided does cause the Swift compiler to crash with a segmentation fault.
– Brent Royal-Gordon
Nov 13 '18 at 0:51
add a comment |
4
Your title says you have a segmentation fault which is a runtime error but your question says you have a compile time error. Which is it? If you have a runtime error, show code that actually causes the error.
– rmaddy
Nov 8 '18 at 5:08
I checked, and the code Shohin provided does cause the Swift compiler to crash with a segmentation fault.
– Brent Royal-Gordon
Nov 13 '18 at 0:51
4
4
Your title says you have a segmentation fault which is a runtime error but your question says you have a compile time error. Which is it? If you have a runtime error, show code that actually causes the error.
– rmaddy
Nov 8 '18 at 5:08
Your title says you have a segmentation fault which is a runtime error but your question says you have a compile time error. Which is it? If you have a runtime error, show code that actually causes the error.
– rmaddy
Nov 8 '18 at 5:08
I checked, and the code Shohin provided does cause the Swift compiler to crash with a segmentation fault.
– Brent Royal-Gordon
Nov 13 '18 at 0:51
I checked, and the code Shohin provided does cause the Swift compiler to crash with a segmentation fault.
– Brent Royal-Gordon
Nov 13 '18 at 0:51
add a comment |
1 Answer
1
active
oldest
votes
This looks like it's a bug in the Swift compiler. (Any time a build fails and there's a crash report instead of an error message, it's a bug.) Please file it with either Apple or Swift open source, and please include your very nice reduced test case, which will save somebody hours of work!
answered Nov 13 '18 at 1:38
Brent Royal-Gordon
13.3k54781
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%2f53201834%2fsegmentation-fault-11-xcode-10-1%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
This looks like it's a bug in the Swift compiler. (Any time a build fails and there's a crash report instead of an error message, it's a bug.) Please file it with either Apple or Swift open source, and please include your very nice reduced test case, which will save somebody hours of work!
answered Nov 13 '18 at 1:38
Brent Royal-Gordon
13.3k54781
add a comment |
This looks like it's a bug in the Swift compiler. (Any time a build fails and there's a crash report instead of an error message, it's a bug.) Please file it with either Apple or Swift open source, and please include your very nice reduced test case, which will save somebody hours of work!
answered Nov 13 '18 at 1:38
Brent Royal-Gordon
13.3k54781
add a comment |
This looks like it's a bug in the Swift compiler. (Any time a build fails and there's a crash report instead of an error message, it's a bug.) Please file it with either Apple or Swift open source, and please include your very nice reduced test case, which will save somebody hours of work!
answered Nov 13 '18 at 1:38
Brent Royal-Gordon
13.3k54781
This looks like it's a bug in the Swift compiler. (Any time a build fails and there's a crash report instead of an error message, it's a bug.) Please file it with either Apple or Swift open source, and please include your very nice reduced test case, which will save somebody hours of work!
answered Nov 13 '18 at 1:38
Brent Royal-Gordon
13.3k54781
answered Nov 13 '18 at 1:38
Brent Royal-Gordon
13.3k54781
answered Nov 13 '18 at 1:38
Brent Royal-Gordon
13.3k54781
answered Nov 13 '18 at 1:38
Brent Royal-Gordon
13.3k54781
13.3k54781
add a comment |
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f53201834%2fsegmentation-fault-11-xcode-10-1%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
4
Your title says you have a segmentation fault which is a runtime error but your question says you have a compile time error. Which is it? If you have a runtime error, show code that actually causes the error.
– rmaddy
Nov 8 '18 at 5:08
I checked, and the code Shohin provided does cause the Swift compiler to crash with a segmentation fault.
– Brent Royal-Gordon
Nov 13 '18 at 0:51