Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FIX] visibility errors on gcc #1228

Closed
wants to merge 7 commits into from

Conversation

marehr
Copy link
Member

@marehr marehr commented Aug 26, 2019

This PR fixes a variant of a visibility bug of gcc.

Apparently, if you use the short-notation for concepts in templates, like this,

template <typename Iterator, Sentinel<Iterator>>
struct foo;

all private/protected members of classes are accessible.

Currently blocked by #1222 and #1225

@codecov
Copy link

codecov bot commented Sep 4, 2019

Codecov Report

Merging #1228 into master will not change coverage.
The diff coverage is 100%.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #1228   +/-   ##
=======================================
  Coverage   97.37%   97.37%           
=======================================
  Files         221      221           
  Lines        8928     8928           
=======================================
  Hits         8694     8694           
  Misses        234      234
Impacted Files Coverage Δ
include/seqan3/range/views/translate_join.hpp 100% <ø> (ø) ⬆️
include/seqan3/alphabet/nucleotide/concept.hpp 100% <ø> (ø) ⬆️
include/seqan3/alphabet/concept.hpp 100% <ø> (ø) ⬆️
include/seqan3/argument_parser/argument_parser.hpp 98.54% <ø> (ø) ⬆️
include/seqan3/alphabet/structure/concept.hpp 100% <ø> (ø) ⬆️
include/seqan3/alphabet/quality/concept.hpp 100% <ø> (ø) ⬆️
.../seqan3/alphabet/composite/alphabet_tuple_base.hpp 100% <ø> (ø) ⬆️
include/seqan3/range/container/small_string.hpp 98.48% <100%> (ø) ⬆️
include/seqan3/range/container/small_vector.hpp 99.25% <100%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update cfea39c...590eb4a. Read the comment docs.

@marehr
Copy link
Member Author

marehr commented Sep 6, 2019

@smehringer Can you have a look? Thank you <3

Copy link
Member

@smehringer smehringer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some questions

@@ -78,7 +78,7 @@ void to_rank(args_t ...) = delete;
//!\brief Functor definition for seqan3::to_rank.
struct to_rank_fn
{
private:
public:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why do the impl function need to be public? As I understand it, they are only used by the operator()?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because the require statement in gcc only allows public statements; clang on the other hand allows this code.

Not sure if this is a bug/workaround, but @h-2 said that I should not bother, because it is detail anyway.

@@ -495,7 +495,7 @@ class argument_parser
*/
argument_parser_meta_data info;

private:
protected:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought we want to befriend a test fixture?
(any way you forgot the //!\privatesection)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants